[Bugs] [Bug 1773991] New: Bricks are not available when volume create fails

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1773991

            Bug ID: 1773991
           Summary: Bricks are not available when volume create fails
           Product: GlusterFS
           Version: 7
                OS: Linux
            Status: NEW
         Component: glusterd
          Assignee: bugs at gluster.org
          Reporter: spamecha at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
If volume creation fails, glusterd reports bricks to be part of volume.

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


How reproducible:
Always


Steps to Reproduce:
1.Fail to create a volume for some reason.
2 Trigger the create command again with same bricks.


Actual results:
[root at dhcp42-109 glusterfs]# gluster v info
No volumes present
[root at dhcp42-109 glusterfs]# gluster v create test-vol1 replica 3
10.70.42.109:/home/gluster/b8 10.70.42.109:/home/gluster/b7
10.70.42.109:/home/gluster/b6
volume create: test-vol1: failed: Multiple bricks of a replicate volume are
present on the same server. This setup is not optimal. Bricks should be on
different nodes to have best fault tolerant configuration. Use 'force' at the
end of the command if you want to override this behavior. 
[root at dhcp42-109 glusterfs]# gluster v create test-vol1 replica 3
10.70.42.109:/home/gluster/b8 10.70.42.109:/home/gluster/b7
10.70.42.109:/home/gluster/b6
volume create: test-vol1: failed: /home/gluster/b8 is already part of a volume
[root at dhcp42-109 glusterfs]# gluster v info
No volumes present


Expected results:
If no volume is created, the brick should be available

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.