Bug 1837933

Summary:	[machines] When using the volumes in NFS storage pool to create a VM, there will be a "Permission denied" error
Product:	Red Hat Enterprise Linux 8	Reporter:	YunmingYang <yunyang>
Component:	cockpit	Assignee:	Martin Pitt <mpitt>
Status:	NEW ---	QA Contact:	YunmingYang <yunyang>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.7	CC:	kkoukiou, leiwang, mpitt, skobyda, wshi, xchen, ymao
Target Milestone:	rc	Keywords:	Reopened
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:	2023-08-16 07:28:33 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 YunmingYang 2020-05-20 08:39:22 UTC

Description of problem:
When trying to use a volume in NFS storage pool to create a VM, a "Permission denied" error raised

Version-Release number of selected component (if applicable):
cockpit-machines-195.8-2.el7_9.x86_64
libvirt-dbus-1.3.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Prepare a NFS storage pool and some volumes in it
2.Use the volumes in the NFS storage pool to create a VM(Need to check "Immediately Start VM")

Actual results:
There will be an "Permission denied" error raised

Expected results:
The VM creation should be successful

Additional info:

Comment 3 YunmingYang 2021-03-02 08:49:38 UTC

Can be reproduced in RHEL-8.4 with follow version package:
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64
cockpit-238.1-1.el8.x86_64
cockpit-machines-238.1-1.el8.noarch

Comment 5 RHEL Program Management 2021-11-20 07:27:00 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 8 RHEL Program Management 2022-07-20 07:27:53 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 11 RHEL Program Management 2023-01-20 07:27:39 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 14 RHEL Program Management 2023-08-16 07:28:33 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.