[Bugs] [Bug 1445407] remove bug-1421590-brick-mux-reuse-ports.t
bugzilla at redhat.com
bugzilla at redhat.com
Thu Apr 27 10:52:56 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1445407
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17116 committed in release-3.10 by
Raghavendra Talur (rtalur at redhat.com)
------
commit 0a59320775ec44c472f9027b0838ad162e0e4f6c
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Tue Apr 11 09:25:48 2017 +0530
tests: remove tests/bugs/core/bug-1421590-brick-mux-reuse-ports.t
bug-1421590-brick-mux-reuse-ports.t seems to be a bad test to me and here
is my
reasoning:
This test tries to check if the ports are reused or not. When a volume is
restarted, by the time glusterd tries to allocate a new port to the one of
the
brick processes of the volume there is no guarantee that the older port
will be
allocated given the kernel might take some extra time to free up the port
between
this time frame. From
https://build.gluster.org/job/regression-test-burn-in/2932/console we can
clearly see that post restart of the volume, glusterd allocated port 49153
&
49155 for brick1 & brick2 respectively but the test was expecting the ports
to
be matched with 49155 & 49156 which were allocated before the volume was
restarted.
>Reviewed-on: https://review.gluster.org/17033
>Smoke: Gluster Build System <jenkins at build.gluster.org>
>NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
>CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
>Reviewed-by: Amar Tumballi <amarts at redhat.com>
>(cherry picked from commit 1612355327fa5f86078b9dbcf7a38e4e0c63e205)
Change-Id: Id887bf28445261d4de04fc7502e58057659c9512
BUG: 1445407
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: https://review.gluster.org/17116
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list