[ https://issues.apache.org/jira/browse/AMBARI-18138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15418919#comment-15418919 ]
Hadoop QA commented on AMBARI-18138: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12823474/AMBARI-18138.patch against trunk revision . {color:red}-1 patch{color}. Top-level trunk compilation may be broken. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8401//console This message is automatically generated. > 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)