----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/32168/#review76778 -----------------------------------------------------------
ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py <https://reviews.apache.org/r/32168/#comment124446> Can you explain how the smokeuser is different than the smokeuser principal? Should the commands be executed as the principal instead of the user? - Jonathan Hurley On March 17, 2015, 2:59 p.m., Robert Levas wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/32168/ > ----------------------------------------------------------- > > (Updated March 17, 2015, 2:59 p.m.) > > > Review request for Ambari, Andrew Onischuk, Jonathan Hurley, and Vitalyi > Brodetskyi. > > > Bugs: AMBARI-10101 > https://issues.apache.org/jira/browse/AMBARI-10101 > > > Repository: ambari > > > Description > ------- > > When Kerberos is enabled, Hive components show alerts due to the following > error: > > ``` > 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 > ``` > > 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. > > > Diffs > ----- > > > ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_metastore.py > 804ddfe > > ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/alerts/alert_hive_thrift_port.py > 0fb8898 > > Diff: https://reviews.apache.org/r/32168/diff/ > > > Testing > ------- > > Manually testing is cluster by setting the smoke user principal name to > something other than `${cluster-env/smokeuser}@${realm}` and saw that alerts > for Hive were working as designed. > > > Thanks, > > Robert Levas > >
