ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin Jetly" <>
Subject Re: Review Request 21300: AMBARI-5726. Adding Oozie failed at service check
Date Sat, 10 May 2014 03:05:19 GMT

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

(Updated May 10, 2014, 3:05 a.m.)

Review request for Ambari, Srimanth Gunturi and Yusaku Sako.


message change corrected "needs to be" to "need to be"

Bugs: AMBARI-5726

Repository: ambari


This happens because HDFS and YARN/MapReduce requires to be restarted for Oozie smoke test
to pass successfully
As a fix to this issue:
1)Don't run smoke test on "Install, Start and Test" page of the add service wizard.
2) Review page should ask user to restart all stale services.

Apart from the above mentioned fixes, the patch also makes sure that Add service wizard just
starts services that are selected in the "Add service wizard" instead of starting all services
in INSTALLED state. Earlier I discovered that if we have stopped services in the cluster and
try to add a new service then along with the new added services other stopped service are
also started by the wizard.

Diffs (updated)

  ambari-web/app/messages.js bf1cab9 



Tested the patch on a cluster with ambari-1.6.0 branch bits.


Jaimin Jetly

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