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

Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration

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

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 2.2.0
    • ambari-upgrade
    • None

    Description

      AMBARI-13295 fixed an issue where, with custom usernames/principals, the Accumulo client was using the default principal to try to authenticate with the Accumulo services with Kerberos enabled. This failed as the client had incorrect information to complete the authentication handshake.

      This issue still exists in 2.1.2, however, which causes an upgrade from 2.1.2 to 2.1.3-SNAPSHOT to fail because the incorrect configuration is never corrected.

      Robert Levas has kindly pointed that the UpgradeCatalog needs to be changed to ensure that the configuration is updated in the upgrade path out of 2.1.2.

      Attachments

        Issue Links

        Activity

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

          People

            elserj Josh Elser
            elserj Josh Elser
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment