Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.5.2
-
None
Description
STR:
- On last step (Start and Test services) of Enable Kerberos wizard dismiss the wizard
Expected behavior: This should only dismiss the wizard and cluster should be kerberized successfully
Actual behavior: UI makes disable kerberos API call when services are being started. This does server side operation for disable kerberos and marks kerberos security type as none. This puts cluster in inconsistent state with ambari showing cluster as non-kerberized and service configs having kerberos settings.