[Bugs] [Bug 1445407] New: remove bug-1421590-brick-mux-reuse-ports.t

[bugzilla at redhat.com]

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

            Bug ID: 1445407
           Summary: remove bug-1421590-brick-mux-reuse-ports.t
           Product: GlusterFS
           Version: 3.10
         Component: tests
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: bugs at gluster.org
        Depends On: 1441035



+++ This bug was initially created as a clone of Bug #1441035 +++

Description of problem:

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.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2017-04-10 23:57:36 EDT ---

REVIEW: https://review.gluster.org/17033 (tests: remove
tests/bugs/core/bug-1421590-brick-mux-reuse-ports.t) posted (#1) for review on
master by Atin Mukherjee (amukherj at redhat.com)

--- Additional comment from Worker Ant on 2017-04-12 03:09:13 EDT ---

COMMIT: https://review.gluster.org/17033 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit 1612355327fa5f86078b9dbcf7a38e4e0c63e205
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.

    Change-Id: Id887bf28445261d4de04fc7502e58057659c9512
    BUG: 1441035
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    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>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1441035
[Bug 1441035] remove bug-1421590-brick-mux-reuse-ports.t
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.