[
https://issues.apache.org/jira/browse/AMBARI-13179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902588#comment-14902588
]
Hudson commented on AMBARI-13179:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #575 (See
[https://builds.apache.org/job/Ambari-branch-2.1/575/])
AMBARI-13179. Cannot edit configs after making older config as current
(onechiporenko) (onechiporenko:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=95e0145c52703d31ae3cbf5007c8d2b8820cf66b)
* ambari-web/app/mixins/common/configs/configs_loader.js
> Cannot edit configs after making older config as current
> --------------------------------------------------------
>
> Key: AMBARI-13179
> URL: https://issues.apache.org/jira/browse/AMBARI-13179
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.2
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-13179.patch
>
>
> STR:
> - Go back a couple of config versions
> - Hit Make V5 current, lets say
> - All configs readonly and force user to create a CG
> - After page refresh configs are editable again
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
