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

Hadoop QA commented on AMBARI-9977:
-----------------------------------

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

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

This message is automatically generated.

> Could not enable RM HA (RM start is failed) after Ambari only upgrade from 
> 1.6.0 to 2.0.0 and enabling NN HA
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9977
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9977
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9977.patch
>
>
> STR:
> 1)Deploy old version with all services
> 2)Make ambari only upgrade to 2.0.0
> 3)Enable NN HA
> 4)Enable RM HA
> Expected result:
> RM HA was enabled.
> Actual result
> Start services failed when enabling RM HA. (RM start failed)



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

Reply via email to