[
https://issues.apache.org/jira/browse/AMBARI-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15116448#comment-15116448
]
Hudson commented on AMBARI-14792:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4224 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4224/])
AMBARI-14792. Install Wizard: remove persist request after step7 (akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e9eed7ea89e6c8b53f59016b0c949e9927946c46])
* ambari-web/app/routes/installer.js
> Install Wizard: remove persist request after step7
> --------------------------------------------------
>
> Key: AMBARI-14792
> URL: https://issues.apache.org/jira/browse/AMBARI-14792
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.4.0
>
> Attachments: AMBARI-14792.patch
>
>
> For example a use case, that may cause unexpected behavior:
> 1. Go to Install Wizard.
> 2. Proceed to step7. Change some configs and click next.
> 3. Relogin.
> 4. Proceed to step7 (again, as relogin resets all the progress).
> 5. Go to Manage Ambari.
> 6. Click on Ambari logo on the top left.
> You will be redirected back to step7, but all configs will be changed, like
> you changed them, when you come to step7 first time (because they were
> persisted). Also all other settings (hosts, service/components selections and
> assignments) will be loaded from your first visit of the wizard. It even may
> be not obvious, that something has changed and user may proceed next and
> after deploy see, that cluster was deployed with wrong settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
