Bug 1366203

Summary:	set volume options before starting the volume
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gdeploy	Assignee:	Devyani Kota <dkota>
Status:	CLOSED ERRATA	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, musoni, rcyriac, rhinduja, rhs-bugs, smohan, storage-qa-internal, surs
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.3 Async
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gdeploy-2.0.1-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-07 11:34:26 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:	1351528

Description SATHEESARAN 2016-08-11 09:53:09 UTC

Description of problem:
-----------------------
When the volume section is mentioned in the gdeploy conf file along with the set of volume options, volume is actually started and then those options are set on the volume.

Its a good practice to set the list of volume options on the volume and then to start the volume.

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

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

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

Actual results:
---------------
volume is started and then the options are set on the volume

Expected results:
-----------------
volume options should be set on the volume and then the volume should be started

Comment 1 SATHEESARAN 2016-09-21 16:42:03 UTC

This is hard requirement for setting up SSL/TLS configuration on the volume.

Comment 3 Sachidananda Urs 2016-10-25 10:58:18 UTC

Commit: https://github.com/gluster/gdeploy/commit/405025b8c0 resolves the issue.
This bug was fixed as part of resolving github issue. Should be available in the latest build. 2.0.1-2

Comment 5 SATHEESARAN 2016-11-07 08:03:13 UTC

Tested with ansible-2.2 and gdeploy-2.0.1-2.el7rhgs

Volume options are first set on the volume and then the volume is started.

Here is snip from the logs to prove the same
<snip>

TASK [Sets options for volume] *************************************************
changed: [host1.example.com] => (item={u'key': u'group', u'value': u'virt'})

PLAY RECAP *********************************************************************
dhcp37-172.lab.eng.blr.redhat.com : ok=1    changed=1    unreachable=0    failed=0   


PLAY [master] ******************************************************************

TASK [Starts a volume] *********************************************************
changed: [host1.example.com]

</snip>

Comment 7 errata-xmlrpc 2017-02-07 11:34:26 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/RHSA-2017-0260.html