[AMBARI-14734] RU/EU, add PreCheck to prevent starting upgrade if a previous upgrade skipped the step Save DB State

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.1
• Component/s: ambari-server
• Assignee: Alejandro Fernandez
• Reporter: Alejandro Fernandez
• Created: 20/Jan/16 03:12
• Updated: 22/Jan/16 00:08
• Resolved: 21/Jan/16 19:17

Description

Customer quit on Save Cluster State and finalized the upgrade later without running "ambari-server set-current --cluster-name=$CLUSTERNAME --version-display-name=$VERSION_NAME".

Next upgrade from 2.3.2 to 2.3.4 deleted configs from desired stack 2.2

STR:
RU/EU HDP 2.2->2.3 (don't Save Cluster State so that desired stack remains on 2.2)
RU/EU from HDP 2.3.0.0-2.3.4.0 and Downgrade (this will remove the configs for the desired stack, which is still 2.2!)

Need stronger prechecks to prevent starting RU/EU if the previous upgrade did not have a downgrade path and the "Save Cluster State" step is not COMPLETED.

Issue Links

• links to: Code Review patch