ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley" <>
Subject Review Request 31177: WebHCat Server Status Alert Does Not Work After Enabling Kerberos
Date Thu, 19 Feb 2015 02:43:45 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for Ambari, Nate Cole and Tom Beerbower.

Bugs: AMBARI-9697

Repository: ambari


After enabling Kerberos, the WebHCat Server Status alert is always CRITICAL. This is caused
by two problems:

1) The lack of any kinit and curl combination when the cluster is kerberized
2) Assuming that cluster-env/security_enabled means SSL (which is does not!)

Consulted with the Kerberos folks that cluster-env/security_enabled is used to indicate kerberization.

It appears that WebHCat doesn't have an SSL mode; So going back to the 1.7.0 alert with a
hard-coded http:// scheme for now.





Tested in a kerberized cluster to ensure that the changed code fixed the CRITICAL alert. Took
the service down to verify that the alert triggered correctly. 

Tested the alert in a regular cluster to ensure the non-kerberized path worked as it has in
the past.


Jonathan Hurley

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message