Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.0.0
Description
This appears to be happening when the KDC and/or KDC Admin hosts do not point to a valid KDC, and when the relevant KDC does not handle the indicated realm.
For the host issue, (in the cases that I tested), a org.apache.ambari.server.serveraction.kerberos.KerberosKDCConnectionException is being thrown but not caught to re-throw a java.lang.IllegalArgumentException, which would generate the expected 400 error.
For the realm issue, the following error string is not being captured by the logic to produce a org.apache.ambari.server.serveraction.kerberos.KerberosRealmException.
kadmin: Cannot find KDC for requested realm while initializing kadmin interface
In any case, org.apache.ambari.server.serveraction.kerberos.KerberosRealmException is not being caught to re-throw a java.lang.IllegalArgumentException, which would generate the expected 400 error.