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.
+++ This bug was initially created as a clone of Bug #1744484 +++
Description of problem:
If create a raw disk in advance, then attach it to the VM through the UI. The attaching is failed with an error message,that is 'operation failed: Incorrect disk format'.
Version-Release number of selected component (if applicable):
cockpit-machines-197.2-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+3531+2918145b.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create an raw disk by using 'virsh vol-create-as $pool $disk $capacity --format raw'
2. Login cockpit and Create a VM
3. Switch to the disk tab of the VM, then click attach button
4. Switch the raw disk which is prepared in advance from 'Using existing'
Actual results:
1. The attaching is failed with an error message that is 'operation failed: Incorrect disk format'.
Expected results:
1. The raw disks which have been created can be attached
Additional info:
--- Additional comment from Simon Kobyda on 2019-08-26 18:52:14 CST ---
This bug was already fixed and merged 19 days ago
commit 0eba27e0735c5eba1edbfed4d29237adf6d4249e
Author: Simon Kobyda <skobyda>
Date: Thu Aug 1 13:27:59 2019 +0200
machines: Fix incorrect disk format when attaching existing volume
If you attach existing volume as a disk, default storage pool format
would be used as disk format. That's however not correct, as we should
use volume's format type as a disk's format type.
Pool's default format type should be used only as a fallback when volume's
format type is not present.
Test Versions:
cockpit-machines-195.5-2.el7.x86_64
libvirt-dbus-1.3.0-1.el7.x86_64
Test Steps:
1. Create an raw disk by using 'virsh vol-create-as $pool $disk $capacity --format raw'
2. Login cockpit and Create a VM
3. Switch to the disk tab of the VM, then click attach button
4. Switch the raw disk which is prepared in advance from 'Using existing'
Test Results:
The disk can be attached to the VM after step 4
According to the results, move the status to VERIFIED.
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-2020:1219