Bug 1476957

Summary: peer-parsing.t fails on NetBSD
Product: [Community] GlusterFS Reporter: Csaba Henk <csaba>
Component: testsAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: NetBSD   
Whiteboard:
Fixed In Version: glusterfs-3.13.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-08 17:36:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Csaba Henk 2017-07-31 23:35:21 UTC
Description of problem:

$ uname -a
NetBSD bab 7.0.2 NetBSD 7.0.2 (GENERIC.201610210724Z) i386
$ sudo env DEBUG=1 ./run-tests.sh ./tests/basic/peer-parsing.t

... GlusterFS Test Framework ...

/mnt/scratch/glusterfs /mnt/scratch/glusterfs
/mnt/scratch/glusterfs

================================================================================
[23:30:28] Running tests in file ./tests/basic/peer-parsing.t
./tests/basic/peer-parsing.t ..
1..8
=========================
TEST 1 (line 6): mkdir -p /var/lib/glusterd/peers
ok 1, LINENUM:6
RESULT 1: 0
=========================
TEST 2 (line 36): create_random_peer_files
ok 2, LINENUM:36
RESULT 2: 0
=========================
TEST 3 (line 37): create_non_peer_file
ok 3, LINENUM:37
RESULT 3: 0
=========================
TEST 4 (line 38): create_random_peer_files
ok 4, LINENUM:38
RESULT 4: 0
=========================
TEST 5 (line 39): create_malformed_peer_file
ok 5, LINENUM:39
RESULT 5: 0
=========================
TEST 6 (line 40): create_random_peer_files
ok 6, LINENUM:40
RESULT 6: 0
=========================
TEST 7 (line 43): glusterd
ok 7, LINENUM:43
RESULT 7: 0
=========================
TEST 8 (line 45): [ 0 = 30 ]
not ok 8 , LINENUM:45
RESULT 8: 1
Failed 1/8 subtests

Test Summary Report
-------------------
./tests/basic/peer-parsing.t (Wstat: 0 Tests: 8 Failed: 1)
  Failed test:  8
Files=1, Tests=8, 21 wallclock secs ( 0.04 usr  0.04 sys +  1.50 cusr  3.31 csys =  4.89 CPU)
Result: FAIL
./tests/basic/peer-parsing.t: bad status 1

       *********************************
       *       REGRESSION FAILED       *
       * Retrying failed tests in case *
       * we got some spurious failures *
       *********************************

./tests/basic/peer-parsing.t ..
1..8
=========================
TEST 1 (line 6): mkdir -p /var/lib/glusterd/peers
ok 1, LINENUM:6
RESULT 1: 0
=========================
TEST 2 (line 36): create_random_peer_files
ok 2, LINENUM:36
RESULT 2: 0
=========================
TEST 3 (line 37): create_non_peer_file
ok 3, LINENUM:37
RESULT 3: 0
=========================
TEST 4 (line 38): create_random_peer_files
ok 4, LINENUM:38
RESULT 4: 0
=========================
TEST 5 (line 39): create_malformed_peer_file
ok 5, LINENUM:39
RESULT 5: 0
=========================
TEST 6 (line 40): create_random_peer_files
ok 6, LINENUM:40
RESULT 6: 0
=========================
TEST 7 (line 43): glusterd
ok 7, LINENUM:43
RESULT 7: 0
=========================
TEST 8 (line 45): [ 0 = 30 ]
not ok 8 , LINENUM:45
RESULT 8: 1
Failed 1/8 subtests

Test Summary Report
-------------------
./tests/basic/peer-parsing.t (Wstat: 0 Tests: 8 Failed: 1)
  Failed test:  8
Files=1, Tests=8, 21 wallclock secs ( 0.07 usr  0.02 sys +  1.71 cusr  3.03 csys =  4.83 CPU)
Result: FAIL
End of test ./tests/basic/peer-parsing.t
================================================================================


Run complete
================================================================================
Number of tests found:                             118
Number of tests selected for run based on pattern: 1
Number of tests skipped as they were marked bad:   0
Number of tests skipped because of known_issues:   0
Number of tests that were run:                     1

Tests ordered by time taken, slowest to fastest:
================================================================================
./tests/basic/peer-parsing.t  -  21 second

1 test(s) failed
./tests/basic/peer-parsing.t

0 test(s) generated core


Result is 1

Comment 1 Worker Ant 2017-07-31 23:40:21 UTC
REVIEW: https://review.gluster.org/17937 (tests: fix hardcoded path in basic/peer-parsing.t) posted (#1) for review on master by Csaba Henk (csaba)

Comment 2 Worker Ant 2017-08-01 00:39:09 UTC
REVIEW: https://review.gluster.org/17937 (tests: don't use hard coded values for glusterd workdir) posted (#2) for review on master by Csaba Henk (csaba)

Comment 3 Worker Ant 2017-08-01 00:39:38 UTC
REVIEW: https://review.gluster.org/17937 (tests: don't use hard coded value for glusterd workdir) posted (#3) for review on master by Csaba Henk (csaba)

Comment 4 Worker Ant 2017-08-02 20:56:21 UTC
COMMIT: https://review.gluster.org/17937 committed in master by Jeff Darcy (jeff.us) 
------
commit c7e5741f938e24b85976bf78ea7d84984a4e1e61
Author: Csaba Henk <csaba>
Date:   Tue Aug 1 01:38:00 2017 +0200

    tests: don't use hard coded value for glusterd workdir
    
    A number of test referred to /var/lib/glusterd,
    they were adjusted to use "$GLUSTERD_WORKDIR".
    
    (This has significance for proper test runs on non-Linux
    platforms -- see the following #define in glusterfs.h:
    
      #ifdef GF_LINUX_HOST_OS
      #define GLUSTERD_DEFAULT_WORKDIR DATADIR "/lib/glusterd"
      #else
      #define GLUSTERD_DEFAULT_WORKDIR DATADIR "/db/glusterd"
      #endif
    
    Ie. the glusterd workdir will typically be /var/db/glusterd
    instead of /var/lib/glusterd on non-Linux platforms.)
    
    BUG: 1476957
    Change-Id: I69ce3e1bb7a0c14ea85b60adbf8205f9aca46cd5
    Signed-off-by: Csaba Henk <csaba>
    Reviewed-on: https://review.gluster.org/17937
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Amar Tumballi <amarts>
    Tested-by: Amar Tumballi <amarts>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Jeff Darcy <jeff.us>

Comment 5 Shyamsundar 2017-12-08 17:36:32 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-3.13.0, please open a new bug report.

glusterfs-3.13.0 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] http://lists.gluster.org/pipermail/announce/2017-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/