Alejandro Fernandez created AMBARI-15673:
--------------------------------------------
Summary: Stack Upgrade did not completely ABORT in-progress
upgrade before orchestrating Downgrade, need to relax 'suspended' property and
keep API backward compatible
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
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".
However, the UI was passing "status=ABORTED" & "suspended=false". In order to
keep the UI and system tests working, will make the API backward compatible so
that "suspended" can have any value.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
