[ 
https://issues.apache.org/jira/browse/AMBARI-14792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115703#comment-15115703
 ] 

Hadoop QA commented on AMBARI-14792:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12784195/AMBARI-14792.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5048//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5048//console

This message is automatically generated.

> 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)

Reply via email to