Bug 1581746 - bug-1309462.t is failing reliably due to changes in security.capability changes in the kernel
Summary: bug-1309462.t is failing reliably due to changes in security.capability chang...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tests
Version: 3.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1581735
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-23 14:39 UTC by Shyamsundar
Modified: 2018-10-23 14:42 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.12.10
Clone Of: 1581735
Environment:
Last Closed: 2018-10-23 14:42:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shyamsundar 2018-05-23 14:39:33 UTC
+++ This bug was initially created as a clone of Bug #1581735 +++

Description of problem:

Repeated failures of the following nature on the regression setup,

./tests/bugs/fuse/bug-1309462.t .. 
1..19
ok 1, LINENUM:14
ok 2, LINENUM:15
ok 3, LINENUM:18
ok 4, LINENUM:19
ok 5, LINENUM:22
ok 6, LINENUM:25
ok 7, LINENUM:27
ok 8, LINENUM:28
ok 9, LINENUM:30
ok 10, LINENUM:33
setfattr: /mnt/glusterfs/0/testfile: Invalid argument
not ok 11 , LINENUM:35
FAILED COMMAND: setfattr -n security.capability -v value /mnt/glusterfs/0/testfile
/mnt/glusterfs/0/testfile: security.capability: No such attribute
not ok 12 , LINENUM:36
FAILED COMMAND: getfattr -n security.capability /mnt/glusterfs/0/testfile
setfattr: /mnt/glusterfs/0/testfile: No such attribute
not ok 13 , LINENUM:37
FAILED COMMAND: setfattr -x security.capability /mnt/glusterfs/0/testfile
ok 14, LINENUM:39
ok 15, LINENUM:42
setfattr: /mnt/glusterfs/0/testfile: Invalid argument
not ok 16 , LINENUM:44
FAILED COMMAND: setfattr -n security.capability -v value /mnt/glusterfs/0/testfile
/mnt/glusterfs/0/testfile: security.capability: No such attribute
not ok 17 , LINENUM:45
FAILED COMMAND: getfattr -n security.capability /mnt/glusterfs/0/testfile
setfattr: /mnt/glusterfs/0/testfile: No such attribute
not ok 18 , LINENUM:46
FAILED COMMAND: setfattr -x security.capability /mnt/glusterfs/0/testfile
ok 19, LINENUM:48
Failed 6/19 subtests 

Root caused to changes introduced by: https://lwn.net/Articles/726273/

Marking the test as BAD, till a resolution is found!

--- Additional comment from Worker Ant on 2018-05-23 10:18:43 EDT ---

REVIEW: https://review.gluster.org/20069 (test: Marking test case bug-1309462.t as bad) posted (#1) for review on master by Shyamsundar Ranganathan

--- Additional comment from Worker Ant on 2018-05-23 10:33:00 EDT ---

COMMIT: https://review.gluster.org/20069 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- test: Marking test case bug-1309462.t as bad

Details in the bug

Updates: bz#1581735

Change-Id: Id984e10b60daf274d5510e3ccbf7abf0cb19f368
Signed-off-by: ShyamsundarR <srangana>

Comment 1 Worker Ant 2018-05-23 17:13:57 UTC
COMMIT: https://review.gluster.org/20072 committed in release-3.12 by "Shyamsundar Ranganathan" <srangana> with a commit message- test: Marking test case bug-1309462.t as bad

Details in the bug

Updates: bz#1581746

Change-Id: Id984e10b60daf274d5510e3ccbf7abf0cb19f368
Signed-off-by: ShyamsundarR <srangana>
(cherry picked from commit 92839c5a4a6c87973e4f6f2f96b359e9c2a0f5c0)

Comment 2 Shyamsundar 2018-10-23 14:42:11 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.12.10, please open a new bug report.

glusterfs-3.12.10 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://lists.gluster.org/pipermail/announce/2018-May/000099.html
[2] https://www.gluster.org/pipermail/gluster-users/


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