Description of problem: Today, setup_cluster yum installs the ambari-agent on all storage nodes, and the ambari-server on the mgmt node, even if they have been previously installed and are running. It would be more flexible if the user had the ability to override this default behavior. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The --force-ambari-update option was added to setup_cluster.sh, and the default behavior of setup_cluster.sh was changed such that if ambari is running it will not be reinstalled. --force-ambari-update overrides this new default behavior.
Tested with versions: rhs-hadoop-install-2_28-1.el6rhs.noarch rhs-hadoop-2.3.3-3.el6rhs.noarch ambari-agent-1.6.1-98.x86_64 ambari-server-1.6.1-98.noarch I tried to run setup_cluster.sh again on properly installed and configured cluster. Script was running only few minutes without option --force-ambari-update and it did not reinstalled ambari. With --force-ambari-update option it ran ~15 minutes and reinstalled ambari agents and server. Process of reinstallation could be seen in /var/log/rhs-hadoop-install.log. After that, on <MANAGEMENT_SERVER>:8080 was first page of setup cluster wizzard. This is behaviour I was expecting -> VERIFIED.
Jeff, Could you please provide the doc text in the Doc Text field for this bug?
Jeff, Could you please review the edited doc text for technical accuracy and sign-off?
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2014-1275.html
(In reply to Divya from comment #6) > Jeff, > > Could you please review the edited doc text for technical accuracy and > sign-off? done