ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13889) Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration
Date Fri, 13 Nov 2015 18:36:11 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated AMBARI-13889:
--------------------------------
    Attachment: AMBARI-13889.001.patch

[~rlevas], any chance you could take a look at this? I haven't run a full suite of tests,
but UpgradeCatalog213Test is passing with the new addition.

> Upgrade from 2.1.2 to 2.1.3 fails with Security enabled due to missing Accumulo configuration
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13889
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13889
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-upgrade
>            Reporter: Josh Elser
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13889.001.patch
>
>
> 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.
> [~rlevas] 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message