Bug 1622649
Summary: | [RHEL7] Some of the Posix compliance tests are failing on gluster mount | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Manisha Saini <msaini> | |
Component: | posix | Assignee: | Raghavendra Bhat <rabhat> | |
Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> | |
Severity: | high | Docs Contact: | ||
Priority: | urgent | |||
Version: | rhgs-3.4 | CC: | amukherj, apaladug, atumball, ndevos, rhs-bugs, sanandpa, sankarshan, sheggodu, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Regression, ZStream | |
Target Release: | RHGS 3.4.z Batch Update 1 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.12.2-20 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1632119 (view as bug list) | Environment: | ||
Last Closed: | 2018-10-31 08:46:14 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: | ||||
Bug Depends On: | 1610966 | |||
Bug Blocks: | 1632119 |
Description
Manisha Saini
2018-08-27 16:37:39 UTC
chmod/00.t and mknod/03.t are expected failures Test results on 3.3.1 gluster build # rpm -qa | grep gluster glusterfs-libs-3.8.4-54.15.el7.x86_64 glusterfs-3.8.4-54.15.el7.x86_64 glusterfs-fuse-3.8.4-54.15.el7.x86_64 glusterfs-client-xlators-3.8.4-54.15.el7.x86_64 Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/chmod/00.t (Wstat: 0 Tests: 106 Failed: 2) Failed tests: 31, 39 /home/ntfs-3g-pjd-fstest/tests/mknod/03.t (Wstat: 0 Tests: 12 Failed: 9) Failed tests: 1-3, 5-7, 9-11 Files=210, Tests=2328, 208 wallclock secs ( 3.38 usr 1.16 sys + 29.52 cusr 68.20 csys = 102.26 CPU) Result: FAIL When only failed cases are run on gluster mount on 3.4 build- mkdir/00.t,mknod/00.t,/utime/02.t test is passing. ====== [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mkdir/00.t /home/ntfs-3g-pjd-fstest/tests/mkdir/00.t .. ok All tests successful. Files=1, Tests=36, 2 wallclock secs ( 0.03 usr 0.01 sys + 0.10 cusr 0.22 csys = 0.36 CPU) Result: PASS [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mknod/00.t /home/ntfs-3g-pjd-fstest/tests/mknod/00.t .. ok All tests successful. Files=1, Tests=36, 2 wallclock secs ( 0.04 usr 0.00 sys + 0.11 cusr 0.23 csys = 0.38 CPU) Result: PASS [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mknod/01.t /home/ntfs-3g-pjd-fstest/tests/mknod/01.t .. Failed 10/27 subtests Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/mknod/01.t (Wstat: 0 Tests: 27 Failed: 10) Failed tests: 12-21 Files=1, Tests=27, 0 wallclock secs ( 0.04 usr 0.00 sys + 0.10 cusr 0.18 csys = 0.32 CPU) Result: FAIL [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mknod/02.t /home/ntfs-3g-pjd-fstest/tests/mknod/02.t .. Failed 6/12 subtests Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/mknod/02.t (Wstat: 0 Tests: 12 Failed: 6) Failed tests: 5-7, 9-11 Files=1, Tests=12, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.04 cusr 0.09 csys = 0.16 CPU) Result: FAIL [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mknod/03.t /home/ntfs-3g-pjd-fstest/tests/mknod/03.t .. Failed 9/12 subtests Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/mknod/03.t (Wstat: 0 Tests: 12 Failed: 9) Failed tests: 1-3, 5-7, 9-11 Files=1, Tests=12, 0 wallclock secs ( 0.03 usr 0.01 sys + 0.08 cusr 0.08 csys = 0.20 CPU) Result: FAIL [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mknod/08.t /home/ntfs-3g-pjd-fstest/tests/mknod/08.t .. Failed 8/35 subtests Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/mknod/08.t (Wstat: 0 Tests: 35 Failed: 8) Failed tests: 16-19, 21-24 Files=1, Tests=35, 1 wallclock secs ( 0.02 usr 0.01 sys + 0.12 cusr 0.22 csys = 0.37 CPU) Result: FAIL [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/mknod/11.t /home/ntfs-3g-pjd-fstest/tests/mknod/11.t .. 8/28 stat returned -1 /home/ntfs-3g-pjd-fstest/tests/mknod/../misc.sh: line 115: [: ENOENT: integer expression expected stat returned -1 /home/ntfs-3g-pjd-fstest/tests/mknod/../misc.sh: line 115: [: ENOENT: integer expression expected stat returned -1 /home/ntfs-3g-pjd-fstest/tests/mknod/../misc.sh: line 115: [: ENOENT: integer expression expected /home/ntfs-3g-pjd-fstest/tests/mknod/11.t .. 21/28 stat returned -1 /home/ntfs-3g-pjd-fstest/tests/mknod/../misc.sh: line 115: [: ENOENT: integer expression expected stat returned -1 /home/ntfs-3g-pjd-fstest/tests/mknod/../misc.sh: line 115: [: ENOENT: integer expression expected stat returned -1 /home/ntfs-3g-pjd-fstest/tests/mknod/../misc.sh: line 115: [: ENOENT: integer expression expected /home/ntfs-3g-pjd-fstest/tests/mknod/11.t .. Failed 24/28 subtests Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/mknod/11.t (Wstat: 0 Tests: 28 Failed: 24) Failed tests: 2-6, 8-19, 21-27 Files=1, Tests=28, 2 wallclock secs ( 0.03 usr 0.00 sys + 0.09 cusr 0.15 csys = 0.27 CPU) Result: FAIL [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/symlink/00.t /home/ntfs-3g-pjd-fstest/tests/symlink/00.t .. Failed 2/14 subtests Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/symlink/00.t (Wstat: 0 Tests: 14 Failed: 2) Failed tests: 11-12 Files=1, Tests=14, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.05 cusr 0.10 csys = 0.17 CPU) Result: FAIL [root@rhs-client6 gluster]# prove -r /home/ntfs-3g-pjd-fstest/tests/utime/02.t /home/ntfs-3g-pjd-fstest/tests/utime/02.t .. ok All tests successful. Files=1, Tests=30, 1 wallclock secs ( 0.03 usr 0.00 sys + 0.09 cusr 0.20 csys = 0.32 CPU) Result: PASS I will attach the logs shortly Marking this as regression as the issue was not seen with 3.3.1 Gluster build Verified this with glusterfs-3.12.2-20.el7rhgs.x86_64 Test Summary Report ------------------- /home/ntfs-3g-pjd-fstest/tests/chmod/00.t (Wstat: 0 Tests: 106 Failed: 2) Failed tests: 31, 39 /home/ntfs-3g-pjd-fstest/tests/mknod/03.t (Wstat: 0 Tests: 12 Failed: 9) Failed tests: 1-3, 5-7, 9-11 Files=210, Tests=2328, 148 wallclock secs ( 1.44 usr 0.58 sys + 14.26 cusr 33.29 csys = 49.57 CPU) Result: FAIL other then chmod/00.t and mknod/03.t test failures,which are expected,no other failures were observed. Moving this BZ to verified state Just curious about this statement:
> other then chmod/00.t and mknod/03.t test failures,which are expected,no other failures were observed.
IMO, it would be good to fix the scripts which makes sense for the stack, and keep it 100% successful, so you can 'automate' it. Any failure in future should be easily caught, and shouldn't be waiting for someone to test. That is possible only when we have 100% success rate with these scripts.
My recommendation is, host the same repo somewhere, and send a patch to fix these 2 failures for glusterfs, and then use that always!
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:3432 |