[jira] [Commented] (AMBARI-9872) Check Kerberos failed after Ambari upgrade 1.7.0->2.0.0

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343615#comment-14343615 ] 

Hadoop QA commented on AMBARI-9872:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12701909/AMBARI-9872.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1878//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1878//console

This message is automatically generated.

> 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 ambari-qa@EXAMPLE.COM' 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 ambari-qa@EXAMPLE.COM;
> kinit: Client not found in Kerberos database while getting initial credentials
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)