[
https://issues.apache.org/jira/browse/AMBARI-17703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376197#comment-15376197
]
Hadoop QA commented on AMBARI-17703:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12817861/AMBARI-17703.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7824//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7824//console
This message is automatically generated.
> Hosts page: after component filter hosts have wrong list of components
> ----------------------------------------------------------------------
>
> Key: AMBARI-17703
> URL: https://issues.apache.org/jira/browse/AMBARI-17703
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Richard Zang
> Assignee: Richard Zang
> Fix For: 2.4.0
>
> Attachments: AMBARI-17703.patch
>
>
> Go to Hosts page, filter by component.
> Result: each host has only filtered component.
> Filtering by stack version produce the same behavior too.
> Filtering by sub-resource should be carry out in two calls, as it was before
> new filter were introduced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
