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

bugzilla at redhat.com bugzilla at redhat.com
Mon Oct 8 12:20:07 UTC 2018


--- Comment #7 from Atin Mukherjee <amukherj at redhat.com> ---
Steps to verify:

Create multiple 1 X 3 volumes with brick multiplexing.

1. Make sure the parent brick (the first brick instance with which the brick
process is spawned up) is disconnected with glusterd.
2. keep sending volume stop request for other volumes
3. (with out the fix) volume will be stopped where as it ideally shouldn't be
as there are brick instances which aren't been detached and this will lead to
stale brick instances which can be proved by running unmount of the brick which
will fail. With the fix, the volume stop will fail.

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=3mhPyT8Zp9&a=cc_unsubscribe

More information about the Bugs mailing list