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:
Storage pool should not be deleted successfully when the volume in it is still used(attached) by VM.
Version-Release number of selected component (if applicable):
cockpit-machines-197-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare a iscsi-pool and add it in the Storage Pools
2. Prepare a VM, open the Disks tab, click Add Disk , choose Use Existing and select the volume in iscsi-pool
4. Click Add and check the disk has been attached to the vm correctly.
5. Enter the Storage Pools Page, and delete the iscsi-pool.
Actual results:
The iscsi-pool is deleted successfully.
Expected results:
It should not be deleted and a prompt error message is needed to tell the user that there is still volume in the pool been using by VM.
Additional info:
Some concern when Deactivate the pool.
commit 67f32a7fe4ef148353d3b0c69a7135f94b8a42d5
Author: Simon Kobyda <42733240+skobyda.github.com>
Date: Thu Aug 8 13:23:13 2019 +0200
machines: Limit pool deletion if pool/volumes are used by any VM
$ git describe 67f32a7fe4ef148353d3b0c69a7135f94b8a42d5
200-9-g67f32a7fe
Verified with package:
cockpit-machines-197.2-1.el8.noarch
Steps:
1. Prepare a iscsi-pool and add it in the Storage Pools
2. Prepare a VM, open the Disks tab, click Add Disk , choose Use Existing and select the volume in iscsi-pool
4. Click Add and check the disk has been attached to the vm correctly.
5. Enter the Storage Pools Page, and delete the iscsi-pool.
The delete button is gray and there is a prompt showing that the volume is used by vm and can not be deleted.
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-2019:3325