[Bugs] [Bug 1458569] New: Regression test for add-brick failing with brick multiplexing enabled
bugzilla at redhat.com
bugzilla at redhat.com
Sun Jun 4 13:19:20 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1458569
Bug ID: 1458569
Summary: Regression test for add-brick failing with brick
multiplexing enabled
Product: Red Hat Gluster Storage
Version: 3.3
Component: glusterd
Assignee: amukherj at redhat.com
Reporter: amukherj at redhat.com
QA Contact: bmekala at redhat.com
CC: bugs at gluster.org, rhs-bugs at redhat.com,
sbairagy at redhat.com, storage-qa-internal at redhat.com,
vbellur at redhat.com
Depends On: 1456898
+++ This bug was initially created as a clone of Bug #1456898 +++
tests/bugs/glusterd/bug-1406411-fail-add-brick-on-replica-count-change.t
(verifies if add-brick functionality works correctly while changing the replica
count simulataneously) is failing on centos machines with brick-multiplexing
enabled.
--- Additional comment from Worker Ant on 2017-05-30 12:23:40 EDT ---
REVIEW: https://review.gluster.org/17422 (glusterd: Fix regression wrt
add-brick on replica count change) posted (#1) for review on master by
Samikshan Bairagya (samikshan at gmail.com)
--- Additional comment from Worker Ant on 2017-05-30 12:56:40 EDT ---
REVIEW: https://review.gluster.org/17422 (glusterd: Fix regression wrt
add-brick on replica count change) posted (#2) for review on master by
Samikshan Bairagya (samikshan at gmail.com)
--- Additional comment from Worker Ant on 2017-05-31 09:19:10 EDT ---
REVIEW: https://review.gluster.org/17422 (glusterd: Fix regression wrt
add-brick on replica count change) posted (#3) for review on master by
Samikshan Bairagya (samikshan at gmail.com)
--- Additional comment from Worker Ant on 2017-06-01 06:46:42 EDT ---
COMMIT: https://review.gluster.org/17422 committed in master by Atin Mukherjee
(amukherj at redhat.com)
------
commit 6b36b162f45c4dfeb5eac21e3d77a27216e089bc
Author: Samikshan Bairagya <samikshan at gmail.com>
Date: Tue May 30 18:09:01 2017 +0530
glusterd: Fix regression wrt add-brick on replica count change
tests/bugs/glusterd/bug-1406411-fail-add-brick-on-replica-count-change.t
was failing on centos machines with brick multiplexing enabled.
This is because detaching individual bricks manually from the
backend like it is done in the regression test framework by
'kill_brick', fails to send a RPC_CLNT_DISCONNECT to glusterd when
multiplexing is enabled. This causes the add-brick command to not
fail when one of the bricks are killed using kill_brick in the
regression test framework. To fix this, set the brick status to
GF_BRICK_STOPPED on the glusterd end during portmap signout. This
commit also sets the brick status in glusterd_brick_stop() function
so that the brick status is correctly set to 'stopped' even when the
function is called independently for individual bricks.
Change-Id: I4d6f7b579069d0cfa53cb2b0cff78876e1f31594
BUG: 1456898
Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
Reviewed-on: https://review.gluster.org/17422
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>
Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1456898
[Bug 1456898] Regression test for add-brick failing with brick multiplexing
enabled
--
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=xqJHM2GGlL&a=cc_unsubscribe
More information about the Bugs
mailing list