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 1666825 - [machines] Cannot import qcow2 VM image to create a new VM.
Summary: [machines] Cannot import qcow2 VM image to create a new VM.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.1
Assignee: Martin Pitt
QA Contact: YunmingYang
URL:
Whiteboard:
: 1681102 1703251 (view as bug list)
Depends On: 1678935
Blocks: 1701002
TreeView+ depends on / blocked
 
Reported: 2019-01-16 16:50 UTC by Bimal Chollera
Modified: 2020-11-14 14:44 UTC (History)
10 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:35 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 Knowledge Base (Solution) 3922291 0 Install None Cannot import qcow2 VM image to create a new VM via cockpit. 2019-02-19 07:08:36 UTC
Red Hat Knowledge Base (Solution) 3938181 0 Supportability None How can I select an existing image disk to boot up or create a VM in cockpit UI ? 2019-02-25 16:08:26 UTC
Red Hat Product Errata RHBA-2019:3325 0 None None None 2019-11-05 20:41:46 UTC

Description Bimal Chollera 2019-01-16 16:50:58 UTC
Description of problem:

No import feature to import a qcow image to create a new VM.

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

cockpit-system-184-1.el8.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Andreas Nilsson 2019-02-15 13:21:17 UTC
Upstream issue with design proposal attached.
https://github.com/cockpit-project/cockpit/issues/11163

Comment 2 Martin Pitt 2019-02-25 16:07:25 UTC
Being implemented in https://github.com/cockpit-project/cockpit/pull/11206

Comment 3 Martin Pitt 2019-02-25 16:08:26 UTC
*** Bug 1681102 has been marked as a duplicate of this bug. ***

Comment 6 Martin Pitt 2019-04-26 06:56:58 UTC
*** Bug 1703251 has been marked as a duplicate of this bug. ***

Comment 7 YunmingYang 2019-05-30 11:18:25 UTC
Test Versions:
cockpit-machines-193-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64


Test Steps:
1.Create VM with using 'Existing Disk Image' for its installation source type and inputting a qcow2 path for its installation source.
2.Run the VM


Test Results:
1.The VM can be created correctly
2.The VM can run correctly


According to the results, cockpit-machines can import qcow2 VM image to create a new VM. So move the status to VERIFIED.

Comment 9 errata-xmlrpc 2019-11-05 20:41:35 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.