Bug 1151211

Summary:	[RFE] setup_cluster should not, by default, yum install ambari (agent/server) when already installed
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Jeff Vance <jvance>
Component:	rhs-hadoop-install	Assignee:	Jeff Vance <jvance>
Status:	CLOSED ERRATA	QA Contact:	Ondřej Komárek <okomarek>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.0	CC:	bchilds, divya, eboyd, esammons, jvance, matt, mkudlej, nlevinki, okomarek
Target Milestone:	Release Candidate	Keywords:	FutureFeature, Triaged, UpcomingRelease, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.24	Doc Type:	Enhancement
Doc Text:	Previously, executing setup_cluster.sh script reinstalled Ambari even if Ambari was running. Now, with this release, executing setup_cluster.sh script does not reinstall Ambari.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-24 11:55:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1159155

Description Jeff Vance 2014-10-09 19:27:30 UTC

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:

Comment 1 Jeff Vance 2014-10-09 19:29:11 UTC

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.

Comment 4 Ondřej Komárek 2014-11-07 12:20:05 UTC

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.

Comment 5 Divya 2014-11-14 08:29:28 UTC

Jeff,

Could you please provide the doc text in the Doc Text field for this bug?

Comment 6 Divya 2014-11-21 08:29:40 UTC

Jeff,

Could you please review the edited doc text for technical accuracy and sign-off?

Comment 7 errata-xmlrpc 2014-11-24 11:55:22 UTC

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

Comment 8 Jeff Vance 2014-12-02 01:58:20 UTC

(In reply to Divya from comment #6)
> Jeff,
> 
> Could you please review the edited doc text for technical accuracy and
> sign-off?

done