[
https://issues.apache.org/jira/browse/AMBARI-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343642#comment-14343642
]
Hudson commented on AMBARI-9872:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #1920 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1920/])
AMBARI-9872. Check Kerberos failed after Ambari upgrade
1.7.0->2.0.0.(vbrodetskyi) (vbrodetskyi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d54457c20376bebcee6a2a8b7051567701b75cc9)
*
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/GenericDbmsHelper.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog200.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/DbmsHelper.java
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog200Test.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessorImpl.java
* ambari-server/src/main/java/org/apache/ambari/server/orm/DBAccessor.java
> 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
>
> Attachments: AMBARI-9872.patch
>
>
> 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)
