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:
If there is no storage pool, there will be an error when deleting a VM with its disk. The error is "no storage vol with matching path $vol_path".

Version-Release number of selected components (if applicable):
cockpit-234-1.el8.x86_64
cockpit-machines-235-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64

How reproducible:
100%

Steps to Reproduce:
1 Prepare a VM, and delete all storage pools.
2 Click the "Delete" button of the VM
3 Check the disk shown on the dialog
4 Click "Delete" button on the dialog

Actual results:
1 There will be an error shown on the dialog, that is "o storage vol with matching path $vol_path"

Expected results: 
1 The VM can be deleted correctly without error.

Additional info:

This is the same  error, or at least the same root cause, as bug 1912384. We already have a PR for that, it just did not land yet. Marking a duplicate. Thanks!

*** This bug has been marked as a duplicate of bug 1912384 ***