This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2213429 - [Machines] The vm can not be deleted with internal&external snapshot
Summary: [Machines] The vm can not be deleted with internal&external snapshot
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: cockpit-machines
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Simon Kobyda
QA Contact: Xianghua Chen
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-08 07:07 UTC by Xianghua Chen
Modified: 2023-09-15 14:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-15 14:13:58 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 Issue Tracker   RHEL-4048 0 None Migrated None 2023-09-15 14:13:50 UTC
Red Hat Issue Tracker RHELPLAN-167607 0 None None None 2023-09-15 14:11:59 UTC

Description Xianghua Chen 2023-06-08 07:07:52 UTC 
Description of problem:
[Machines] The vm can not be deleted with internal&external snapshot

Version-Release number of selected components (if applicable):
cockpit-machines-291-1.el9.noarch
cockpit-292-1.el9.x86_64
libvirt-dbus-1.4.1-5.el9.x86_64
libvirt-client-9.3.0-2.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a vm , like cirros

2. Enter vm details page, click "Create snapshot", fillin :
Name: test1
Description: internal_snapshot

3. On the host, use virsh to create a external_snapshot :
# virsh snapshot-create-as --domain cirros --name test2 --description 'external_snapshot' --disk-only

4. Refresh the vm details page

5. Try to delete the test2, there will be error:
Snapshot test2 could not be deleted
Operation not supported: deleting external snapshot that has internal snapshot as parent not supported

6. Try to delete the test1, there will be error:
Snapshot test1 could not be deleted
Operation not supported: disk image 'vda' for internal snapshot 'test1' is not the same as disk image currently used by VM

7. Try to delete the vm, there will be error:
Danger alert:Could not delete cirros
Operation not supported: deleting external snapshot that has internal snapshot as parent not supported


Actual results:
See step5 & step6 & step7.

Expected results:
Can delete in step5/6/7, at least can delete the vm at last.

Additional info:
Comment 1 Simon Kobyda 2023-06-21 10:33:06 UTC 
Libvirt still doesn't support operations related to external snapshots, and there is nothing we can do about it. See libvirt bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1519002

And the idea behind external/internal snapshots division is that we should be able to use the same APIs for snapshot operations, nevertheless if we are interacting with internal or external snapshot. So once libvirt implements all the operations for external snapshots, they should start working seaminglessly without us having to change anything.

So I think this bugzilla is not really relevant and propose to close it as CLOSED - CANTFIX
Comment 2 Simon Kobyda 2023-06-21 10:34:50 UTC 
Oh wait, now I just realized that we delete snapshots manually when VM is deleted, so we can actually do something about it. Re-opening it
Comment 4 RHEL Program Management 2023-09-15 14:12:02 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-15 14:13:58 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.