Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-13339

Failure To Create A Rolling Upgrade Leaves an Incorrect Desired State

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • trunk
    • None
    • ambari-server
    • None

    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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            dmitriusan Dmitry Lysnichenko
            dmitriusan Dmitry Lysnichenko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment