Bug 1193970 - Fix spurious ssl-authz.t regression failure (backport)
Summary: Fix spurious ssl-authz.t regression failure (backport)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: 3.6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: manu@netbsd.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: glusterfs-3.6.3
TreeView+ depends on / blocked
 
Reported: 2015-02-18 16:12 UTC by Jeff Darcy
Modified: 2016-02-04 15:21 UTC (History)
2 users (show)

Fixed In Version: glusterfs-v3.6.3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-04 15:21:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jeff Darcy 2015-02-18 16:12:14 UTC
The original patch was attached to #1129939, but that's a catch-all for everything related to NetBSD porting so it shouldn't really be cloned for just this one thing.  The patch on master is here:

http://review.gluster.org/#/c/9686/

Comment 1 Anand Avati 2015-02-18 16:15:07 UTC
REVIEW: http://review.gluster.org/9686 (tests/features/ssl-authz.t: Fix spurious failures) posted (#2) for review on release-3.6 by Jeff Darcy (jdarcy)

Comment 2 Anand Avati 2015-02-19 06:57:52 UTC
COMMIT: http://review.gluster.org/9686 committed in release-3.6 by Raghavendra Bhat (raghavendra) 
------
commit 58b71c64308e7680b5fc5326ed1aed294f848ecb
Author: Emmanuel Dreyfus <manu>
Date:   Fri Jan 23 11:24:07 2015 +0100

    tests/features/ssl-authz.t: Fix spurious failures
    
    Fix two spurious failures in tests/features/ssl-authz.t
    1) Wait for bricks to come online after starting a volume, so that
       the mount is usable without "socket not connected" error
    2) For a mount that must fail, we may get the situation where there
       is no mount at all, which means creating a file will write to the
       mount point instead of failing. To cover that case, write the
       file and check it is absent from the brick.
    
    BUG: 1193970
    Change-Id: If95e1d65ab23d11123f778c20f8110a3177b0e7f
    Signed-off-by: Emmanuel Dreyfus <manu>
    Reviewed-on: http://review.gluster.org/9483
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Jeff Darcy <jdarcy>
    Reviewed-on: http://review.gluster.org/9686
    Reviewed-by: Justin Clift <justin>
    Reviewed-by: Raghavendra Bhat <raghavendra>

Comment 3 Kaushal 2016-02-04 15:21:33 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v3.6.3, please open a new bug report.

glusterfs-v3.6.3 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2015-April/021669.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.