[
https://issues.apache.org/jira/browse/AMBARI-15673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Fernandez updated AMBARI-15673:
-----------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Pushed to trunk,
commit fa6550c4ef38f9c15e7a341c02bdac046e0e28d4
Pushed to branch-2.2,
commit 4c6353cf3fdae16fb80bd7042e30676be9e93c31
> 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)
