Vitaly Brodetskyi created AMBARI-9872:
-----------------------------------------
Summary: Check Kerberos failed after Ambari upgrade 1.7.0->2.0.0
Key: AMBARI-9872
URL: https://issues.apache.org/jira/browse/AMBARI-9872
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.0.0
Reporter: Vitaly Brodetskyi
Assignee: Vitaly Brodetskyi
Priority: Blocker
Fix For: 2.0.0
Kerberos check fails
STR:
1. Install Ambari 1.7.0
2. Enable security
3. Upgrade to Ambari 2.0.0
4. Execute Kerberos Wizard.
Start and Test Services fails
{code}
2015-02-26 22:57:58,558 - Error while executing command 'service_check':
Traceback (most recent call last):
File
"/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
line 208, in execute
method(env)
File
"/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/service_check.py",
line 37, in service_check
}, user=params.smoke_user)
File
"/var/lib/ambari-agent/cache/common-services/KERBEROS/1.10.3-10/package/scripts/kerberos_common.py",
line 316, in test_kinit
user = user,
File "/usr/lib/python2.6/site-packages/resource_management/core/base.py",
line 148, in __init__
self.env.run()
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 152, in run
self.run_action(resource, action)
File
"/usr/lib/python2.6/site-packages/resource_management/core/environment.py",
line 118, in run_action
provider_action()
File
"/usr/lib/python2.6/site-packages/resource_management/core/providers/system.py",
line 276, in action_run
raise ex
Fail: Execution of 'kinit -k -t /etc/security/keytabs/smokeuser.headless.keytab
[email protected]' returned 1. kinit: Client not found in Kerberos database
while getting initial credentials
{code}
similar error is for zookeeper start.
Manual execution of this command on any node gives the same result:
{code}
/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
[email protected];
kinit: Client not found in Kerberos database while getting initial credentials
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)