Bug 1679058

Summary:	[machines][RFE] Provide information how and where the ISO files for VM installation are stored
Product:	Red Hat Enterprise Linux 8	Reporter:	Roman Hodain <rhodain>
Component:	cockpit-appstream	Assignee:	Katerina Koukiou <kkoukiou>
Status:	NEW ---	QA Contact:	YunmingYang <yunyang>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8.0	CC:	mpitt, mtessun, ovasik, qiyuan, rhodain, xchen
Target Milestone:	rc	Keywords:	FutureFeature, Reopened
Target Release:	---
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:	2021-02-01 07:33:02 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 Roman Hodain 2019-02-20 09:35:27 UTC

Description of problem:
When installing a VM through the cockpit from an ISO file stored on the filesystem. The interface should tell the user where to store the ISO file and what permissions should be set.

Version-Release number of selected component (if applicable):
cockpit-machines-184.1-1.el8.noarch

How reproducible:
100%

Steps to Reproduce:
1.Install new VM
2.Set iso destination filesystem
3.Set path to /root/....iso

Actual results:
Installation fails

Expected results:
There is information that the iso cannot be read before the installation starts and what should be set to make it work.

Additional info:
Feel free to move it to documentation if you believe that it should be handled there.

Comment 1 Martin Pitt 2019-02-21 15:46:08 UTC

Hello Roman,

I'm afraid I don't understand this yet. Do you mean you set a nonexisting path to an ISO in the dialog, and the error message should become better? Or that you set an existing path and something else went wrong?

Comment 2 Roman Hodain 2019-04-12 13:08:16 UTC

(In reply to Martin Pitt from comment #1)
> Hello Roman,
> 
> I'm afraid I don't understand this yet. Do you mean you set a nonexisting
> path to an ISO in the dialog, and the error message should become better? Or
> that you set an existing path and something else went wrong?

Hi,

the point is that the file has to have the right permissions so the qemu process can read it. There can also be a problem with SELinux. The user may not be aware of this and expects that it works out of the box. So I believe that there should be some guidance on how to prepare the file.

Comment 6 RHEL Program Management 2021-02-01 07:33:02 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.