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

Hadoop QA commented on AMBARI-18935:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12839593/AMBARI-18935-trunk-orig.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-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9325//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9325//console

This message is automatically generated.

> 'HAWQ segments unregistered' shows incorrect alert
> --------------------------------------------------
>
>                 Key: AMBARI-18935
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18935
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>            Reporter: Matt
>            Assignee: Matt
>            Priority: Minor
>             Fix For: trunk, 2.5.0
>
>         Attachments: AMBARI-18935-trunk-orig.patch
>
>
> The alert is caused because of the mismatch in case between HAWQ segment 
> hostnames mentioned in the slaves file and the data stored in the DB



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

Reply via email to