[
https://issues.apache.org/jira/browse/AMBARI-20302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894740#comment-15894740
]
Hudson commented on AMBARI-20302:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1175 (See
[https://builds.apache.org/job/Ambari-branch-2.5/1175/])
AMBARI-20302. Despite user selecting not to apply Config Changes, (akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f5e686b652f359aa4e98c0f6aebdc89fdf527138])
* (edit) ambari-web/app/controllers/main/service/item.js
* (edit) ambari-web/test/controllers/main/service/item_test.js
> Despite user selecting not to apply Config Changes, Changes are being applied
> -----------------------------------------------------------------------------
>
> Key: AMBARI-20302
> URL: https://issues.apache.org/jira/browse/AMBARI-20302
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20302_branch-2.5.patch, AMBARI-20302.patch
>
>
> Steps:
> 1) On an existing cluster, Delete Ambari Infra service
> 2) At time of deletion, there will be a popup which shows Recommended Config
> changes
> 3) Unselect the recommended config change and continue
> Expected:
> Config change should not be applied
> Acutal:
> Config change was applied regardless
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
