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

Hadoop QA commented on AMBARI-17377:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812540/AMBARI-17377.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  org.apache.ambari.server.stack.StackManagerTest
                  
org.apache.ambari.server.api.services.KerberosServiceMetaInfoTest
                  org.apache.ambari.server.api.services.AmbariMetaInfoTest

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

This message is automatically generated.

> Rolling Upgrade process is blocked after ambari-server/ambari-agent restart
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-17377
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17377
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17377.patch
>
>
> Steps to reproduce:
> # Start Rolling Upgrade.
> # Restart ambari-server or ambari-agent.
> Result: operation running during restart will be moved to skipped_failed 
> status, all next - to aborted. After that it is impossible to execute retry 
> or ignore and proceed:
> {code}
> {
>   "status" : 400,
>   "message" : "java.lang.IllegalArgumentException: Can not transition a stage 
> from ABORTED to PENDING"
> }
> {code}



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

Reply via email to