You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2017/08/22 18:18:00 UTC
[jira] [Resolved] (AMBARI-21767) Kerberos cluster - hive service
check failed post migration
[ https://issues.apache.org/jira/browse/AMBARI-21767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Levas resolved AMBARI-21767.
-----------------------------------
Resolution: Cannot Reproduce
I successfully upgraded from Ambari 2.4.2/BI 4.2.5 to Ambari 2.5.2/HDP 2.6.2 without any Hive service check issue - during or after EU.
Trying to generate the error "HTTP/....@... is not allowed to impersonate ambari-qa", I changed the groups for the local ambari-qa account from "hadoop, users" to just "hadoop" and I now get the error.
This appears to be environmental.
> 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
> Assignee: Robert Levas
> 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>
> *WORKAROUND:*
> 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)