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 <jh...@hortonworks.com> on 2015/02/18 21:54:34 UTC
Review Request 31161: Oozie Server Process Alert Does Not Work After
Enabling Kerberos
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31161/
-----------------------------------------------------------
Review request for Ambari, Nate Cole and Tom Beerbower.
Bugs: AMBARI-9695
https://issues.apache.org/jira/browse/AMBARI-9695
Repository: ambari
Description
-------
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')
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.
Diffs
-----
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py cd4d3ed
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/files/alert_check_oozie_server.py 7bf1255
Diff: https://reviews.apache.org/r/31161/diff/
Testing
-------
Deployed in a regular cluster to verify that Oozie check still works. Deployed in a kerberized cluster and verified that the alert was incorrect and that the updated script fixes the problem.
Thanks,
Jonathan Hurley
Re: Review Request 31161: Oozie Server Process Alert Does Not Work
After Enabling Kerberos
Posted by Nate Cole <nc...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31161/#review73010
-----------------------------------------------------------
Ship it!
Ship It!
- Nate Cole
On Feb. 18, 2015, 3:54 p.m., Jonathan Hurley wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/31161/
> -----------------------------------------------------------
>
> (Updated Feb. 18, 2015, 3:54 p.m.)
>
>
> Review request for Ambari, Nate Cole and Tom Beerbower.
>
>
> Bugs: AMBARI-9695
> https://issues.apache.org/jira/browse/AMBARI-9695
>
>
> Repository: ambari
>
>
> Description
> -------
>
> 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')
>
> 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.
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py cd4d3ed
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/files/alert_check_oozie_server.py 7bf1255
>
> Diff: https://reviews.apache.org/r/31161/diff/
>
>
> Testing
> -------
>
> Deployed in a regular cluster to verify that Oozie check still works. Deployed in a kerberized cluster and verified that the alert was incorrect and that the updated script fixes the problem.
>
>
> Thanks,
>
> Jonathan Hurley
>
>
Re: Review Request 31161: Oozie Server Process Alert Does Not Work
After Enabling Kerberos
Posted by Robert Levas <rl...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31161/#review73036
-----------------------------------------------------------
Ship it!
Ship It!
- Robert Levas
On Feb. 18, 2015, 3:54 p.m., Jonathan Hurley wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/31161/
> -----------------------------------------------------------
>
> (Updated Feb. 18, 2015, 3:54 p.m.)
>
>
> Review request for Ambari, Nate Cole and Tom Beerbower.
>
>
> Bugs: AMBARI-9695
> https://issues.apache.org/jira/browse/AMBARI-9695
>
>
> Repository: ambari
>
>
> Description
> -------
>
> 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')
>
> 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.
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py cd4d3ed
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/files/alert_check_oozie_server.py 7bf1255
>
> Diff: https://reviews.apache.org/r/31161/diff/
>
>
> Testing
> -------
>
> Deployed in a regular cluster to verify that Oozie check still works. Deployed in a kerberized cluster and verified that the alert was incorrect and that the updated script fixes the problem.
>
>
> Thanks,
>
> Jonathan Hurley
>
>
Re: Review Request 31161: Oozie Server Process Alert Does Not Work
After Enabling Kerberos
Posted by Tom Beerbower <tb...@hortonworks.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/31161/#review73012
-----------------------------------------------------------
Ship it!
Ship It!
- Tom Beerbower
On Feb. 18, 2015, 8:54 p.m., Jonathan Hurley wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/31161/
> -----------------------------------------------------------
>
> (Updated Feb. 18, 2015, 8:54 p.m.)
>
>
> Review request for Ambari, Nate Cole and Tom Beerbower.
>
>
> Bugs: AMBARI-9695
> https://issues.apache.org/jira/browse/AMBARI-9695
>
>
> Repository: ambari
>
>
> Description
> -------
>
> 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')
>
> 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.
>
>
> Diffs
> -----
>
> ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/alerts/alert_check_oozie_server.py cd4d3ed
> ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/package/files/alert_check_oozie_server.py 7bf1255
>
> Diff: https://reviews.apache.org/r/31161/diff/
>
>
> Testing
> -------
>
> Deployed in a regular cluster to verify that Oozie check still works. Deployed in a kerberized cluster and verified that the alert was incorrect and that the updated script fixes the problem.
>
>
> Thanks,
>
> Jonathan Hurley
>
>