Bug 1313274

Summary:	[RFE] Move `clients' feature out of core-modules
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Sachidananda Urs <surs>
Component:	gdeploy	Assignee:	Nandaja Varma <nvarma>
Status:	CLOSED ERRATA	QA Contact:	Neha <nerawat>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	annair, nvarma, rcyriac, rhinduja, sashinde, smohan
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	RHGS 3.1.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	gdeploy-2.0-2	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-23 05:29:37 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:	1311386

Description Sachidananda Urs 2016-03-01 10:05:58 UTC

Currently `clients' feature is part of core modules and runs after
backend-setup, peer, and volume. 

With new projects like Aplo, the volume can be created by other
modules like kubernets. Since core-modules are executed first,
the clients will be run before kubernetes, which causes mount to
fail. Move the client out of core-modules.

Comment 3 Neha 2016-06-09 07:13:48 UTC

volume setup:

##cat volume_create.conf 

[hosts]
10.70.42.78
10.70.43.40

[backend-setup]
devices=sdb,sdc
vgs=vg1,vg2
pools=pool1,pool2
lvs=lv1,lv2
mountpoints=/mnt/data1,/mnt/data2
brick_dirs=/mnt/data1/1,/mnt/data2/2

[volume]
action=create
volname=testvol
replica=yes
replica_count=2
force=yes

## cat client.conf 
[hosts]
10.70.42.78
10.70.43.40

[clients1]
action=mount
volname=testvol
hosts=10.70.43.139
fstype=glusterfs
client_mount_points=/mnt/testvol

[clients2]
action=mount
volname=testvol
hosts=10.70.43.17
fstype=glusterfs
client_mount_points=/mnt/testvol

Don't see any issue with these configs, moving it to verified

Comment 5 errata-xmlrpc 2016-06-23 05:29:37 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://access.redhat.com/errata/RHEA-2016:1250