Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1761299

Summary: Permission denied when starting guest with image on nfs server and the nfs shared dir containing sticky bit
Product: Red Hat Enterprise Linux 8 Reporter: yafu <yafu>
Component: libvirtAssignee: Michal Privoznik <mprivozn>
Status: CLOSED DUPLICATE QA Contact: yafu <yafu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: chhu, dyuan, lcheng, lmen, rbalakri, xuzhang
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-27 13:36:25 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:
Attachments:
Description Flags
libvirtd log none

Description yafu 2019-10-14 03:15:42 UTC
Description of problem:
Permission denied when starting guest with image on nfs server and the nfs shared dir containing sticky bit.
The issue was caused by Bug 1652078 - RFE: the security drivers must remember original permissions/labels and restore them after
Can not reproduce the issue if disable 'remember_owner' in qemu.conf.


Version-Release number of selected component (if applicable):
libvirt-5.6.0-6.x86_64
qemu-kvm-4.1.0-13.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Setup a nfs-server with shared dir containing sticky bit:
#mkdir /nfs
#chmod 777 /nfs
#chmod o+t /nfs
#mkdir /nfs/nfs-server
#qemu-img create -f qcow2 nfs-server/test.qcow2 100M
#vim /etc/exports
 /nfs/nfs-server  *(async,rw,no_root_squash)
#exportfs -a

2.Mount the nfs shared dir:
#mkdir /nfs/nfs-mount
#mount 127.0.0.1:/nfs/nfs-server /nfs/nfs-mount/

3.Attach the image on nfs server to the guest:
#virsh attach-disk avocado-vt-vm1 /nfs/nfs-server/test.qcow2 sdb --config --subdriver qcow2

4.Start the guest:
# virsh start avocado-vt-vm1
error: Failed to start domain avocado-vt-vm1
error: internal error: child reported (status=125): unable to open /nfs/nfs-mount/test.qcow2: Permission denied

Actual results:
permission denied when starting guest with image on nfs server and the nfs shared dir containing sticky bit

Expected results:
The guest can start successfully.

Additional info:
The guest can start successfully if disable 'remember_owner' in qemu.conf.

Comment 1 Michal Privoznik 2020-01-15 13:36:19 UTC
Yafu, I'm unable to reproduce. Can you please attach debug logs? Also, does this still occur with the latest build?

Comment 2 yafu 2020-01-20 08:41:08 UTC
I can not reproduce with the steps in comment 0, but can reproduce the issue with following steps with libvirt-5.6.0-10.module+el8.1.1+5309+6d656f05.x86_64.

Test steps:
1.Setup a nfs server:
#mkdir /test
#mkdir /test/server
#qemu-img create -f qcow2 /test/server/test.qcow2 100M
#chown qemu:qemu /test/server/test.qcow2
#vim /etc/exports
 /test/server  *(sync,wdelay,hide,no_subtree_check,sec=sys,rw,secure,root_squash,no_all_squash)
#exportfs -a

2.Mount the nfs shared dir:
#mkdir /test/mount
#mount 127.0.0.1:/test/server /test/mount/

3.Attach the image on nfs server to the guest:
#virsh attach-disk avocado-vt-vm1 /test/server/test.qcow2 sdb --config --subdriver qcow2 --config

4.Start the guest:
# virsh start avocado-vt-vm1
error: Failed to start domain avocado-vt-vm1
error: internal error: child reported (status=125): unable to open /test/server/test.qcow2: Permission denied

Comment 3 yafu 2020-01-20 08:48:27 UTC
Created attachment 1653841 [details]
libvirtd log

Comment 4 Michal Privoznik 2020-02-27 13:36:25 UTC

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