[AMBARI-13339] Failure To Create A Rolling Upgrade Leaves an Incorrect Desired State

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 07/Oct/15 13:38
• Updated: 26/Jan/16 01:17
• Resolved: 25/Jan/16 18:51

Description

When creating an upgrade between stack versions (such as HDP 2.2 to 2.3), if the creation of the upgrade fails, then the following data is left in an inconsistent state:

• Cluster Desired Version (still at 2.3)
• Configurations: all new configurations created for 2.3 remain and are set as the desired configuration.

We need to cleanup this data so that a failure to begin the upgrade doesn't leave the cluster in a bad state.

STR:

• Install HDP 2.2
• Get ready to install HDP 2.3 by distributing the repo and resolving pre-req checks
• Determine how you want to cause the failure. In my case, it was a problem while creating all of the states and tasks in the database.
• Try to upgrade; the upgrade will never get created, but all of the 2.3 configs will and the desired states will change.

Issue Links

• links to: Review Board