[
https://issues.apache.org/jira/browse/AMBARI-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-10101:
----------------------------------
Attachment: AMBARI-10101_trunk_01.patch
AMBARI-10101_branch-2.0.0_01.patch
Updated alert logic to use {{cluster-env/smokeuser_principal_name}} when
kinit-ing.
Trunk Patch [^AMBARI-10101_trunk_01.patch]
Branch-2.0.0 Patch [^AMBARI-10101_branch-2.0.0_01.patch]
> Hive alert on secured cluster
> -----------------------------
>
> Key: AMBARI-10101
> URL: https://issues.apache.org/jira/browse/AMBARI-10101
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Robert Levas
> Assignee: Robert Levas
> Priority: Critical
> Labels: alerts, kerbeos
> Fix For: 2.0.0
>
> Attachments: AMBARI-10101_branch-2.0.0_01.patch,
> AMBARI-10101_trunk_01.patch
>
>
> When Kerberos is enabled, Hive components show alerts due to the following
> error:
> {code}
> WARNING 2015-03-16 06:01:08,253 base_alert.py:140 -
> [Alert][hive_metastore_process] Unable to execute alert. Execution of
> '/usr/bin/kinit -kt /etc/security/keytabs/smokeuser.headless.keytab
> ambari-qa; ' returned 1. kinit: Keytab contains no suitable keys for
> ambari-qa@REALM while getting initial credentials
> {code}
> This occurs because the alert logic for Hive uses {{cluster-env/smokeuser}}
> rather than {{cluster-env/smokeuser_principal_name}} to get the principal
> name for the smoke test identity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
