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

Hadoop QA commented on AMBARI-14695:
------------------------------------

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

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

This message is automatically generated.

> HAWQSTANDBY fails to start when HAWQ Service is started
> -------------------------------------------------------
>
>                 Key: AMBARI-14695
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14695
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Matt
>            Assignee: Matt
>             Fix For: trunk, 2.2.1
>
>         Attachments: AMBARI-14695-branch-2-2.patch, AMBARI-14695-trunk.patch
>
>
> Steps to reproduce:
> - Install cluster
> - Install HAWQ service
> - Start HAWQ
> When HAWQ is started, HAWQSTANDBY is started first.
> For HAWQSTANDBY to start successfully, HAWQMASTER has to be in started state.



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

Reply via email to