Bug 1226233

Summary: Mount broker user add command removes existing volume for a mountbroker user when second volume is attached to same user
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: avishwan, bugs, dnarayan, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1226223 Environment:
Last Closed: 2015-06-25 06:03: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: 1226223, 1234869, 1235428    
Bug Blocks: 1233025    

Description Aravinda VK 2015-05-29 09:27:33 UTC
+++ This bug was initially created as a clone of Bug #1226223 +++

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):


How reproducible:
Always

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.
3.

Actual results:
The volume added first is removed from the volfile

Expected results:
The volume added second must be appended to the existing list of volumes for a mount broker user.

Additional info:

Comment 1 Niels de Vos 2015-06-02 08:20:23 UTC
The required changes to fix this bug have not made it into glusterfs-3.7.1. This bug is now getting tracked for glusterfs-3.7.2.

Comment 2 Niels de Vos 2015-06-20 10:08:50 UTC
Unfortunately glusterfs-3.7.2 did not contain a code change that was associated with this bug report. This bug is now proposed to be a blocker for glusterfs-3.7.3.

Comment 3 Darshan 2015-06-25 06:03:37 UTC

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