[ 
https://issues.apache.org/jira/browse/AMBARI-15946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrii Tkach updated AMBARI-15946:
----------------------------------
    Attachment: AMBARI-15946.patch

> Make Current button doesn't work when 2 versions are being compared on Ambari 
> UI
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-15946
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15946
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.2.1.1
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15946.patch, pics (1).docx
>
>
> *PROBLEM:* 
> From ambari UI, we can hover mouse over the previous versions of any configs 
> and we can an option to make it current. This works fine.
> We also have an feature to compare the current and previous versions. When we 
> do this we get a green button *"Make V6 Current"* 
> (V6 is in my cluster. It can be any version). 
> If we click on this we get *"Created from service config version {0}"* pop up 
> and again a Make current button. 
> Click on it and everything seems ok. But the problem is the previous version 
> is NOT made current.
> This works fine on Safari and firefox but *it does NOT work on chrome*.
>  *Attachments:*
>  
>  1. [^pics (1).docx] - screenshots.
> *BUSINESS IMPACT:* This caused us lot of issue as we all thought previous 
> configs had been reinstated but it wasn't and our debugging took a complete 
> detour.
> *Go Live Date -* N/A
> *STEPS TO REPRODUCE:*
> 1. Hover mouse on any previous version and click "compare".
> 2. Click "Make Current V6" (Make current for previous version).
> 3. Make current confirmation pop-up shows version {0} instead of the actual 
> version number.
> 4. Click "Make Current" and restart all services marked for "restart".
> *EXPECTED RESULT:*   The version I choose to make current should be applied.
> *ACTUAL RESULT:* Previous version is not made current.
> *SUPPORT ANALYSIS:* Reproduced the issue in-house.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to