Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Ambari 2.0 remains old Realm after re-enabling Kerberos including Realm change

Solved Go to solution

Ambari 2.0 remains old Realm after re-enabling Kerberos including Realm change

If you disable Kerberos, change the Realm and enable Kerberos afterwards, then Ambari 2.0 versions still wants to use the old Realm.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Ambari 2.0 remains old Realm after re-enabling Kerberos including Realm change

Guru

This is a known bug => https://issues.apache.org/jira/browse/AMBARI-10930

But what to do if you cannot upgrade Ambari but needs to enable Kerberos again with a different Realm ?

You have to remove the remaining Kerberos artifacts by using the following REST call, then you can enable Kerberos with the new Realm applied:

curl -H "X-Requested-By:ambari" -u 
<adminuser>:<adminpw>  -X DELETE http://<ambari-server>:8080/api/v1/clusters/<clustername>/artifacts/kerberos_descriptor
1 REPLY 1

Re: Ambari 2.0 remains old Realm after re-enabling Kerberos including Realm change

Guru

This is a known bug => https://issues.apache.org/jira/browse/AMBARI-10930

But what to do if you cannot upgrade Ambari but needs to enable Kerberos again with a different Realm ?

You have to remove the remaining Kerberos artifacts by using the following REST call, then you can enable Kerberos with the new Realm applied:

curl -H "X-Requested-By:ambari" -u 
<adminuser>:<adminpw>  -X DELETE http://<ambari-server>:8080/api/v1/clusters/<clustername>/artifacts/kerberos_descriptor
Don't have an account?
Coming from Hortonworks? Activate your account here