You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/02/18 21:34:12 UTC
[jira] [Commented] (AMBARI-9695) Oozie Server Process Alert Does
Not Work After Enabling Kerberos
[ https://issues.apache.org/jira/browse/AMBARI-9695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326509#comment-14326509 ]
Jonathan Hurley commented on AMBARI-9695:
-----------------------------------------
It looks like Oozie Server Status was set to use the smokeuser as the principal. This actually ends up using cluster-env/smokeuser - I'm guessing that's not right. We should be using the Oozie principal.
> Oozie Server Process Alert Does Not Work After Enabling Kerberos
> ----------------------------------------------------------------
>
> Key: AMBARI-9695
> URL: https://issues.apache.org/jira/browse/AMBARI-9695
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
>
> Installed HDP 2.2 cluster, all services except Ranger, Spark and Flume.
> Using build #426, three node cluster.
> Enabled kerberos, MIT KDC.
> Crit Alerts for: Oozie Server Status ('smokeuser_principal')
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)