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.
Description of problem:
Some times we must configure a disk as readonly or shareable when adding it
to a guest. These options are currently not present in cockpit-machines
Version-Release number of selected component (if applicable):
kernel-4.18.0-67.el8.x86_64
cockpit-machines-184.1-1.el8.noarch
How reproducible:
100%
Actual results:
There are no options to set a virtual disk to be marked as readonly or
shareable for a guest in cockpit-machines
Expected results:
Provide the mentioned options since virt-manager offers them.
Verified with packages:
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64
Steps:
1. Prepare a VM and keep it shutdown, open Disks page.
2. Click "Add Disk" ,configure as following:
Name:rawdisk1
Size:1 GiB
Format:raw
Click Add.
Check the info page for the new added disk ,the Access column should be Writeable as default.
3. Click "Edit" at the end of the new created raw disk,change to "Writeable and shared", click "Save"
The Access column should be changed to Writeable and shared.
4. Click "Edit" at the end of the new created raw disk,change to "Read-only", click "Save"
The Access column should be changed to Read-only.
5. Prepare another VM and keep it shutdown, open Disks page.
Click "Add Disk" , choose "Use Existing", choose the new created rawdisk in step 2 as Volume
click "Add"
The disk can be attached to the new VM.
The Access column for the new created disk under the 2 VMs should be Writeable and shared.
So 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:1639