ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14841) Filtering hosts with alerts by name gives incorrect results
Date Fri, 29 Jan 2016 19:40:39 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124072#comment-15124072
] 

Hadoop QA commented on AMBARI-14841:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12785165/AMBARI-14841.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {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/5120//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5120//console

This message is automatically generated.

> Filtering hosts with alerts by name gives incorrect results
> -----------------------------------------------------------
>
>                 Key: AMBARI-14841
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14841
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>            Reporter: Daniel Gergely
>            Assignee: Daniel Gergely
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14841.patch
>
>
> Filtering for hostnames in hosts with alerts is not working properly, it returns all
the hosts.
> The cause is the precedence in the request:
> alerts_summary/CRITICAL>0|alerts_summary/WARNING>0&Hosts/host_name.matches(.\*200.\*)
> is applied as:
> critical OR (warning AND match)
> but the correct way would be:
> (critical OR warning) AND match



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message