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:
[Machines] Can not delete the vm with a external disk snapshot
Version-Release number of selected components (if applicable):
cockpit-machines-249-1.el9.noarch
cockpit-250-1.el9.x86_64
libvirt-dbus-1.4.1-4.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a vm
2. Create a snapshot by command, then refresh the vm details page
# virsh snapshot-create-as --domain ${vm_name} --name ${snapshot_name} --description '{Description}' --disk-only
3. Delete the snapshot created in step 3 by clicking 'Delete' button
4. Delete the vm without deleting the image storage file
Actual results:
In step 3, There will be a error shown, which is "unsupported configuration: deletion of 1 external disk snapshots not supported yet"
And the Source file changed to a new image file
In step4, There is also an same error:
VM cirros failed to get deleted
unsupported configuration: deletion of 1 external disk snapshots not supported yet
Expected results:
For the error in step3, will it support deleting external disk snapshot in the future?
Will we support deleting the vm with external disk in step 4?
Please feel free to close this bug if all are expected and no plan on fixing it, as this scenario rarely happen for customer as we used command to create the snapshot but not with UI. Just want to be clarified here.
Additional info:
Latest update:
Package:
cockpit-machines-278-1.el9.noarch
cockpit-280.1-1.el9.x86_64
libvirt-8.10.0-2.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
There will be no error message show in step 4 now, which should better have a clear message to the customer.
Comment 3RHEL Program Management
2023-02-11 07:27:42 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.
I retried this bug with packages:
cockpit-machines-283-1.el9.noarch
cockpit-285-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
libvirt-daemon-9.0.0-3.el9.x86_64
Steps to Reproduce:
1. Prepare a running vm
2. Create a snapshot by command, then refresh the vm details page
# virsh snapshot-create-as --domain ${vm_name} --name ${snapshot_name} --description '{Description}' --disk-only
3. Delete the snapshot created in step 3 by clicking 'Delete' button
The snapshot can be deleted now.
4. Re create the snapshot, then delete the vm without deleting the image storage file
The vm can be deleted now.
So the bug is fixed now.
Hi Katerina, could you set related flags and move it to ON_QA so that I can change it to verified?
Verified with packages:
cockpit-machines-283-1.el9.noarch
cockpit-285-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
libvirt-daemon-9.0.0-3.el9.x86_64
Steps to Reproduce:
1. Prepare a running vm
2. Create a snapshot by command, then refresh the vm details page
# virsh snapshot-create-as --domain ${vm_name} --name ${snapshot_name} --description '{Description}' --disk-only
3. Delete the snapshot created in step 3 by clicking 'Delete' button
The snapshot can be deleted .
4. Re create the snapshot, then delete the vm without deleting the image storage file
The vm can be deleted now.
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 (cockpit-machines bug fix and enhancement update), 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-2023:2211
Description of problem: [Machines] Can not delete the vm with a external disk snapshot Version-Release number of selected components (if applicable): cockpit-machines-249-1.el9.noarch cockpit-250-1.el9.x86_64 libvirt-dbus-1.4.1-4.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. Prepare a vm 2. Create a snapshot by command, then refresh the vm details page # virsh snapshot-create-as --domain ${vm_name} --name ${snapshot_name} --description '{Description}' --disk-only 3. Delete the snapshot created in step 3 by clicking 'Delete' button 4. Delete the vm without deleting the image storage file Actual results: In step 3, There will be a error shown, which is "unsupported configuration: deletion of 1 external disk snapshots not supported yet" And the Source file changed to a new image file In step4, There is also an same error: VM cirros failed to get deleted unsupported configuration: deletion of 1 external disk snapshots not supported yet Expected results: For the error in step3, will it support deleting external disk snapshot in the future? Will we support deleting the vm with external disk in step 4? Please feel free to close this bug if all are expected and no plan on fixing it, as this scenario rarely happen for customer as we used command to create the snapshot but not with UI. Just want to be clarified here. Additional info: