ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-21767) Kerberos cluster - hive service check failed post migration
Date Mon, 21 Aug 2017 17:03:02 GMT

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

Siddharth Wagle commented on AMBARI-21767:
------------------------------------------

Hi [~dili], instead of the workaround we should be doing a Regenerate keytabs right after
EU, we would need to hand-edit and fix quite a few config issues unless we run it. Hence,
we recommend Regenerate to fix these issues.

> Kerberos cluster - hive service check failed post migration
> -----------------------------------------------------------
>
>                 Key: AMBARI-21767
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21767
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.2
>            Reporter: Di Li
>             Fix For: 2.5.2
>
>
> Post migration hive service check failed with following error:
> Templeton Smoke Test (ddl cmd): Failed. : {"error":"User: HTTP/mmk-m-2.fyre.ibm.com@IBM.COM
is not allowed to impersonate ambari-qa"}http_code <500>
> 2017-08-18 09:51:50,109 - Retrying after 5 seconds. Reason: Execution of '/var/lib/ambari-agent/tmp/templetonSmoke.sh
mmk-m-2.fyre.ibm.com ambari-qa 50111 idtest.ambari-qa.1503075103.65.pig /etc/security/keytabs/smokeuser.headless.keytab
true /usr/bin/kinit ambari-qa-m13@IBM.COM /var/lib/ambari-agent/tmp' returned 1. Templeton
Smoke Test (ddl cmd): Failed. : {"error":"User: HTTP/mmk-m-2.fyre.ibm.com@IBM.COM is not allowed
to impersonate ambari-qa"}http_code <500>
> Templeton Smoke Test (ddl cmd): Failed. : {"error":"User: HTTP/mmk-m-2.fyre.ibm.com@IBM.COM
is not allowed to impersonate ambari-qa"}http_code <500>
> Shailaja suggested to modify all the entries in custom core-site property under HDFS
service to *  and also add hbase. I added hbase key value pair as following:
> hadoop.proxyuser.hbase.groups  *     
> hadoop.proxyuser.hbase.hosts  *
> Also modified following properties:
> hadoop.proxyuser.hcat.hosts was  mmk-m-2.fyre.ibm.com modified to *
> hadoop.proxyuser.HTTP.hosts was mmk-m-2.fyre.ibm.com  modified to   *
> hadoop.proxyuser.yarn.hosts was mmk-m-2.fyre.ibm.com   modified to *
> hadoop.proxyuser.knox.groups was users    modified to *
> hadoop.proxyuser.HTTP.groups was users    modified to  *
> hadoop.proxyuser.root.hosts  was  mmk-m-1.fyre.ibm.com  modified  to *
> After that hive service check passed. If this work around is not done bigsql upgrade
will fail during service check. This step is not documented.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message