Bug 1346652

Summary:	Segregate the installation of various required rpms in to a separate conf file
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gdeploy	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	sabose, smohan, surs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-28 10:33:46 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:

Description SATHEESARAN 2016-06-15 07:01:48 UTC

Description of problem:
-----------------------

There is no way to stop the gdeploy configuration, when there is a failure encountered. This leads to bad state of the machine, where lvm commands hang without disabling multipath

The issue will be solved with bug[1] which provides an option for each section to abort on failure. But because that change take a time, the temporary solution is to provide 2 gdeploy config files. One containing all the installation of rpms from the channels. Only when the first step succeeds, user is asked to run the second gdeploy conf file.

Note this will be the temporary solution for the limited availability release

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1346253


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gdeploy-2.0-16


How reproducible:
-----------------
NA

Steps to Reproduce:
-------------------
NA

Actual results:
---------------
NA

Expected results:
-----------------
provide 2 gdeploy config files, with one conf file only installing the required rpms, and other doing all the configurations

Comment 1 SATHEESARAN 2016-06-16 08:20:14 UTC

The solution to provide 2 gdeploy config files is a workaround to provide a way to stop the configuration, when encountered with a failure.

The actual issue is filed in the bz 1341484

Comment 2 Sachidananda Urs 2016-06-23 09:20:18 UTC

With the new hc requirements, we no longer do a yum update or install.
Layered install will not be done in future. The requirement of two
configuration files is no longer needed. Will close once I get confirmation
from sahina@

Comment 3 Sahina Bose 2016-07-28 06:29:15 UTC

I think if we have Bug 1341484 implemented - we don't need to take this bug in, but can close this.

Comment 4 Sachidananda Urs 2016-07-28 10:33:46 UTC

Yes we can close this, this is a duplicate of 1341484.

*** This bug has been marked as a duplicate of bug 1341484 ***

Comment 5 SATHEESARAN 2016-08-08 12:48:36 UTC

Since this bug is close removing all the acks and keywords