ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15673) Stack Upgrade should allow suspended=false when aborting an upgrade to initiate a downgrade
Date Mon, 04 Apr 2016 21:29:25 GMT

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

Hudson commented on AMBARI-15673:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.2 #588 (See [https://builds.apache.org/job/Ambari-branch-2.2/588/])
AMBARI-15673. Stack Upgrade should allow suspended=false when aborting (afernandez: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4c6353cf3fdae16fb80bd7042e30676be9e93c31])
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/UpgradeResourceProvider.java


> Stack Upgrade should allow suspended=false when aborting an upgrade to initiate a downgrade
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15673
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15673
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.2
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15673.branch-2.2.patch, AMBARI-15673.trunk.patch
>
>
> STR:
> * Installed Ambari ambari-server-2.2.2.0-354.x86_64
> * HDP 2.3.0.0-2557
> * Installed bits for HDP 2.4.0.0-169
> * Performed EU
> * It failed on waiting to leave HDFS Safemode, but you can do this on any manual stage,
such as Pre-Finalize; click the "Downgrade" button
> Notice that the current Upgrade did not get ABORTED.
> I had to manually run,
> {code}
> update host_role_command set status = 'ABORTED' WHERE  request_id = ? and status IN ('PENDING',
'HOLDING_FAILED');
> {code}
> Root cause is that UpgradeResourceProvider was expecting both these properties to be
passed as "status=ABORTED" & "suspended=true".
> The UI was passing "status=ABORTED" & "suspended=false", which is correct because
it was used to initiate a Downgrade.



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

Mime
View raw message