[ https://issues.apache.org/jira/browse/AMBARI-21962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169972#comment-16169972 ]
Hadoop QA commented on AMBARI-21962: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12887210/AMBARI-21962.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-web. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12254//console This message is automatically generated. > Components Filter has a preselected component from a deleted conf group while > adding hosts to a new conf group. Hosts listed are not correct either > --------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: AMBARI-21962 > URL: https://issues.apache.org/jira/browse/AMBARI-21962 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Reporter: Ishan Bhatt > Assignee: Ishan Bhatt > Fix For: trunk, 2.6.0 > > Attachments: AMBARI-21962_branch-2.6.patch, AMBARI-21962.patch > > > Create a new config group > Add only NN host to be a member of this group > Update a property and save to this conf group. > Delete this conf group > Now go to Manage config group again to create a new group. While adding hosts > to this config group, click on Components filter to choose a component > (Namenode in this case). Looks like Namenode is already selected (actual.png) > which is not right. Expected to be as in expected.png > Even if namenode is selected the hosts shown on the popup window contains all > nodes in the cluster and not just namenode host. -- This message was sent by Atlassian JIRA (v6.4.14#64029)