-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/35185/
-----------------------------------------------------------
Review request for Ambari, Alejandro Fernandez and Nate Cole.
Bugs: AMBARI-11749
https://issues.apache.org/jira/browse/AMBARI-11749
Repository: ambari
Description
-------
Deployed a clean HDP 2.2 cluster and noticed a 404 NOT FOUND alert for Oozie.
The alert definition has the following:
{code}
"http": "{{oozie-site/oozie.base.url}}/oozie/?user.name=oozie",
{code}
However, {{oozie/site/oozie.base.url}} is {{http://server/oozie}} which makes
the alert look for {{http://server/oozie/oozie?usern.name=oozie}} instead of
{{http://server/oozie?user.name=oozie}}
Either the alert definitions (in both 4.* and 5.* OOZIE folders) needs to
change or the base url property needs to change.
Diffs
-----
ambari-server/src/main/java/org/apache/ambari/server/state/alert/AlertUri.java
c337dec
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
76cd0fc
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/alerts.json
a14f782
ambari-server/src/main/resources/common-services/OOZIE/5.0.0.2.3/alerts.json
d75d1b2
ambari-server/src/main/resources/stacks/BIGTOP/0.8/services/OOZIE/alerts.json
e57a4f8
Diff: https://reviews.apache.org/r/35185/diff/
Testing
-------
mvn clean test
Verified new oozie alert definition does not throw a 404
Thanks,
Jonathan Hurley
