@Sami AhmadSeems the krb5-conf is missing or corrupted.
Please try Manually create the kerberos-env and krb5-conf by issuing the Ambari REST API call explained below:
PUT /api/v1/clusters/CLUSER_NAME
[
{
"Clusters": {
"desired_config": {
"type": "krb5-conf",
"tag": "version1234",
"properties": {
"domains":"",
"manage_krb5_conf": "true",
"conf_dir":"/etc",
"content" : "[libdefaults]\n renew_lifetime = 7d\n forwardable= true\n default_realm = {{realm|upper()}}\n ticket_lifetime = 24h\n dns_lookup_realm = false\n dns_lookup_kdc = false\n #default_tgs_enctypes = {{encryption_types}}\n #default_tkt_enctypes ={{encryption_types}}\n\n{% if domains %}\n[domain_realm]\n{% for domain in domains.split(',') %}\n {{domain}} = {{realm|upper()}}\n{% endfor %}\n{%endif %}\n\n[logging]\n default = FILE:/var/log/krb5kdc.log\nadmin_server = FILE:/var/log/kadmind.log\n kdc = FILE:/var/log/krb5kdc.log\n\n[realms]\n {{realm}} = {\n admin_server = {{admin_server_host|default(kdc_host, True)}}\n kdc = {{kdc_host}}\n }\n\n{# Append additional realm declarations below #}\n"
}
}
}
},
{
"Clusters": {
"desired_config": {
"type": "kerberos-env",
"tag": "version1234",
"properties": {
"kdc_type": "mit-kdc",
"manage_identities": "false",
"install_packages": "true",
"encryption_types": "aes des3-cbc-sha1 rc4 des-cbc-md5",
"realm" : "EXAMPLE.COM",
"kdc_host" : "hdc.host",
"admin_server_host" : "kadmin.host",
"executable_search_paths" : "/usr/bin, /usr/kerberos/bin, /usr/sbin, /usr/lib/mit/bin, /usr/lib/mit/sbin",
"password_length": "20",
"password_min_lowercase_letters": "1",
"password_min_uppercase_letters": "1",
"password_min_digits": "1",
"password_min_punctuation": "1",
"password_min_whitespace": "0",
"service_check_principal_name" : "${cluster_name}-${short_date}",
"case_insensitive_username_rules" : "false"
}
}
}
}
]Note:
manage_identities is set to false indicating that Ambari is to not interact with the KDC. This is because the customer did not want Ambari to destroy the principals in the KDC. Since Ambari was not managing the Kerberos identities, there was no need to fill in the correct data about the KDC.
TIP
When issuing the API call mentioned above, place the payload into a file and use curl like:
curl -H "X-Requested-By:ambari" -u admin:admin -i -X PUT -d @./payload.json http://AMBARI_SEVER:8080/api/v1/clusters/CLUSTER_NAME
