Bug 1596918

Summary: Glusterfs can't set xattr security.selinux
Product: [Community] GlusterFS Reporter: Rixome <r.medina>
Component: coreAssignee: bugs <bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1CC: amukherj, bugs, ndevos, rhs-bugs, sankarshan, smohan, storage-qa-internal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-02 07:37:13 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 Rixome 2018-06-30 06:36:22 UTC
Description of problem:
I'm currently trying to use Gluster as storage for docker volumes on Centos 7.
The gluster version is 4.0.2.

On creation of the volume the files from the container are copied to the new volume. The volume is stored in a gluster mounted directory using the gluster client (no NFS).

Upon copying the first file I get this error: 

    dockerd: time="2018-06-29T16:54:42.0
    5675816+02:00" level=error msg="fatal task error" error="failed to copy xattrs: failed to set xattr \"security.selinux\" on /var/lib/docker/volumes/test_laravelstorage/_data/app/.gitignore: operation not supported" module=node/agent/taskmanager node.id=zfqlnpdchcaa0xl0vs8ck0ec7 dervice.id=e94kmsgqq222ohssk6is866la task.id=k9efjmil9sgmeza507z9r7qy

Selinux is disabled. 


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


How reproducible:

Set xattr security.selinux of file.

Comment 2 Atin Mukherjee 2018-06-30 15:43:25 UTC
As 4.0 is end of life I’m moving this yo mainline for now. Please test this with 4.1 and if you still see it change the version to 4.1.

Comment 3 Rixome 2018-06-30 22:07:45 UTC
I just tried on version 4.1 but I get the same error.

Comment 4 Niels de Vos 2018-07-02 07:37:13 UTC
There is work needed in the Linux kernel, FUSE kernel module and the kernel component of SELinux before this can work. Bug 1230671 tracks the different topics.

*** This bug has been marked as a duplicate of bug 1230671 ***