Description of problem:
Mount broker user add command(gluster system:: execute mountbroker user geoaccount slavevol) removes existing volume for a mountbroker user when second volume is attached to the same mount broker user.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Add a volume to a mount broker user using the above mentioned command.
2.Add another volume to same mount broker user using command.
The volume added first is removed from the volfile
The volume added second must be appended to the existing list of volumes for a mount broker user.
REVIEW: http://review.gluster.org/11385 (geo-rep: Fix add user in mountbroker user management) posted (#1) for review on master by Kotresh HR (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/11385 (geo-rep: Fix add user in mountbroker user management) posted (#2) for review on master by Kotresh HR (email@example.com)
REVIEW: http://review.gluster.org/11424 (doc/admin-guide: Document new CLI in mountbroker user management) posted (#2) for review on master by Kotresh HR (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/11385 committed in master by Venky Shankar (email@example.com)
Author: Kotresh HR <firstname.lastname@example.org>
Date: Thu Jun 25 00:18:01 2015 +0530
geo-rep: Fix add user in mountbroker user management
The CLI 'gluster system:: execute mountbroker user <USERNAME> <VOLUMES>'
to set volumes associated with a user replaces existing user and associated
volumes upon setting with existing user. This patch fixes it by appending
the volumes if the user already exists.
It also introduces following CLI to remove volume for a corresponding user.
'gluster system:: execute mountbroker volumedel <USERNAME> <VOLUME>'
<VOLUME>: comman separated list of volumes to delete
If it is the last volume to be deleted associated with the user,
it will delete the user as well as it doesn't make sense to keep
only user without volumes associated.
Signed-off-by: Kotresh HR <email@example.com>
Reviewed-by: darshan n <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Reviewed-by: Aravinda VK <firstname.lastname@example.org>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.