Bug 1397743 - GDEPLOY+GANESHA] Provide support for adding permissions to more than 1 client in gdeploy
Summary: GDEPLOY+GANESHA] Provide support for adding permissions to more than 1 client...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: ---
Assignee: Devyani Kota
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-23 10:00 UTC by Manisha Saini
Modified: 2018-11-08 06:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-08 06:28:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Manisha Saini 2016-11-23 10:00:38 UTC
Description of problem:
Currently gdeploy works for adding permissions to 1 client only.
Fails to add permissions to more than 1 client.

Version-Release number of selected component (if applicable):
gdeploy-2.0.1-5.el7rhgs.noarch
glusterfs-3.8.4-5.el7rhgs.x86_64

How reproducible:


Steps to Reproduce:
1.Create 4 node ganesha setup using gdeploy
2.Create a volume with nfs enable on that client
3.Mount the volume to client
4.With gdeploy give permissions to 2 or more clients.Run refresh-config

[hosts]
dhcp46-241.lab.eng.blr.redhat.com
dhcp46-219.lab.eng.blr.redhat.com
dhcp47-159.lab.eng.blr.redhat.com
dhcp47-3.lab.eng.blr.redhat.com


[nfs-ganesha]
action=refresh-config
config-block=clients = 10.70.46.60;|allow_root_access = false;|access_type = "RW";|Protocols = "3";|anonymous_uid = 1440;|anonymous_gid = 72;
config-block=clients = 10.70.46.44;|allow_root_access = true;|access_type = "RO";|Protocols = "4";|anonymous_uid = 1440;|anonymous_gid = 72;
volname=ganeshaval


Actual results:
Refresh config fails to provide permissions to more than 1 client

Expected results:
gdeploy should provide permissions to any no. of client and refresh config should work with it.

Additional info:

Comment 6 Sachidananda Urs 2018-10-22 05:37:00 UTC
Since this functionality will be moved to gluster-ansible in future, this bug is flagged for closure. If there is a requirement to fix in 3.x please update the bug.


Note You need to log in before you can comment on or make changes to this bug.