[Bugs] [Bug 1624444] Fail volume stop operation in case brick detach request fails

[bugzilla at redhat.com]

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

Rajesh Madaka <rmadaka at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amukherj at redhat.com,
                   |                            |rmadaka at redhat.com
              Flags|                            |needinfo?(amukherj at redhat.c
                   |                            |om)



--- Comment #8 from Rajesh Madaka <rmadaka at redhat.com> ---
I have followed above steps to verify this bug.

Below are the scenarios tried.

Scenario 1:

1. Created 5 replica(1x3) volumes
2. Detached the brick using "gf_attach -d
/var/run/gluster/3f637a11d12aa168.socket /bricks/brick4/rep_test1" from first
volume for first node.
3. Then that particular brick went to offline from first volume.
4. I have tried to stop the other volumes. volumes stopped successfully but
with fix volume stop should fail.

Scenario 2:

1. Created 5 replica(1x3) volumes
2. Detached the brick using "gf_attach -d
/var/run/gluster/3f637a11d12aa168.socket /bricks/brick4/rep_test1" from first
volume for all 3 nodes.
3. Then three bricks went to offline from first volume.
4. I have tried to stop the other volumes. volumes stopped successfully but
with fix volume stop should fail.

Build: glusterfs-3.12.2-21

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NRJBIz2Rhj&a=cc_unsubscribe