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 1684422 - [machines] Support https://*.iso installation source
Summary: [machines] Support https://*.iso installation source
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 8.1
Assignee: Katerina Koukiou
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-01 08:58 UTC by YunmingYang
Modified: 2020-11-14 13:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:41:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3325 0 None None None 2019-11-05 20:42:06 UTC

Description YunmingYang 2019-03-01 08:58:41 UTC
Description of problem:
Currently,when https://*.iso is used as the installation resource, vm will be created, but installation will fail with the following error:


"Error validating install location: Could not find an installable distribution at 'https://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_64/os/images/boot.iso'.The location must be the root directory of an install tree. See virt-install man page for various distro examples."


As https://*.iso is not supported, in order to be more user friendly, it's better to show a warning message when https://*.iso is used, and disable the create button to terminate vm creation process until correct parameters are setted.

Version-Release number of selected component (if applicable):
cockpit-machines-184.1-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8+2704+d2eddeb5.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Login to cockpit and open Virtual Machines page.
2.Click 'Create VM' button to open the vm creation dialogue window
3.Choose the url as the installation source type
4.Input a https url of iso for the installation source,such as https://download.fedoraproject.org/pub/fedora/linux/releases/28/Server/x86_64/os/images/boot.iso
5.Check 'Immediately Start' checkbox,then click 'Create' button

Actual results:
1. the VM was created,but installation failed with the error above

Expected results:
1.There is a warning saying "https://*.iso is not supported" when https://*.iso is used as the installation source,and the create button should be disabled.

Additional info:

Comment 1 Martin Pitt 2019-03-04 09:47:53 UTC
Katerina, I thought that creating a VM from an iso was supported? We do have the --cdrom install method in the code at least.

This doesn't seem to be an RFE, but an actual bug, so adjusting the title.

Comment 2 Andreas Nilsson 2019-03-08 13:36:19 UTC
Martin, we support installing from local ISO and installing from http OS tree, but not installing a remote ISO served over http.
The UI is probably a bit vague here. Currently it does say URL as the Installation Source Type. Maybe "Installation Tree" or something similar would be clearer. It would also help if the error was inline instead of telling you only after it started creating the VM.

Comment 3 Katerina Koukiou 2019-04-11 08:54:30 UTC
https://github.com/cockpit-project/cockpit/pull/11516

This PR allows using ISOs on URLs.

Comment 5 YunmingYang 2019-05-28 11:10:07 UTC
@Katerina, it seems that this PR is not be merged. Will it be added into rhel8.1.0?

Comment 6 Katerina Koukiou 2019-06-10 11:16:49 UTC
@Yunming this will be available in 8.1.0 (cockpit 196 release).

commit 32924e45d7725859308a592538e0cc1acd3100a4
Author: Simon Kobyda <42733240+skobyda.github.com>
Date:   Mon Jun 10 13:10:48 2019 +0200

    machines: Allow user to supply direct URL of ISO file in VM creation dialog

$ git describe 32924e45d7725859308a592538e0cc1acd3100a4
195-72-g32924e45d

Comment 7 YunmingYang 2019-06-20 02:56:00 UTC
Test Versions:
cockpit-machines-196-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64


Test Steps:
1.Create and install the VM by using https iso


Test Results:
1. The creation and installation of the VM is successful.


According to the results, move the status to VERIFIED.

Comment 9 errata-xmlrpc 2019-11-05 20:41:55 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3325


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