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-11939) Upgrades Placed Into ABORTED Status Show As COMPLETED
Date Tue, 16 Jun 2015 11:13:00 GMT

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

Hadoop QA commented on AMBARI-11939:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12739755/AMBARI-11939.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/3194//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3194//console

This message is automatically generated.

> Upgrades Placed Into ABORTED Status Show As COMPLETED
> -----------------------------------------------------
>
>                 Key: AMBARI-11939
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11939
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11939.patch
>
>
> When placing a stack upgrade request into the ABORTED state, Ambari calculates the stages
and overall request as COMPLETED even though the tasks are actually ABORTED.
> This prevents that request from being placed back into the PENDING state.
> - Now this upgrade can be aborted:
> {code:title=PUT api/v1/clusters/<cluster>/upgrades/21}
> {
>   "Upgrade": {
>     "request_status": "ABORTED"
>   }
> }
> {code}
> - At this point, experimental mode can be enabled to work with Ambari. When finalize
is ready, the same upgrade/request can be placed back into a {{PENDING}} status:
> {code:title=PUT api/v1/clusters/<cluster>/upgrades/21}
> {
>   "Upgrade": {
>     "request_status": "PENDING"
>   }
> }
> {code}



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

Mime
View raw message