[
https://issues.apache.org/jira/browse/AMBARI-18138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419119#comment-15419119
]
Hudson commented on AMBARI-18138:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5515 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5515/])
AMBARI-18138. Overriding a config in a Config group and then saving it
(akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=25506aeb53123cde7cca6f1aa1056ab9cdc06f8d])
* ambari-web/test/mixins/common/configs/configs_loader_test.js
* ambari-web/app/mixins/common/configs/configs_loader.js
* ambari-web/app/controllers/main/service/info/configs.js
> Overriding a config in a Config group and then saving it transitions the
> screen to default group with configs in non-editable state
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-18138
> URL: https://issues.apache.org/jira/browse/AMBARI-18138
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-18138.patch, AMBARI-18138_branch-2.4.patch
>
>
> *STR:*
> # On a deployed cluster, Create a config group for any servce
> # Select the config group. All configs will show up in non-editable state
> # Override any config, change the overridden value and save configurations.
> *Actual Result:* After saving, Default group appears with non-editable state.
> *Expected Result:* Either Default group should appear in editable state or
> config group should appear in non-editable state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
