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.
.Adding improvements to Virtual Machines configuration
With this update, the RHEL 8 web console includes a lot of improvements in the Virtual Machines page. You can now:
* Manage various types of storage pools
* Configure VM autostart
* Import existing qcow images
* Install VMs through PXE boot
* Change memory allocation
* Pause/resume VMs
* Configure cache characteristics (directsync, writeback)
* Change the boot order
Description of problem:
1] After removing the mount point from the host, it is not possible to stop/ delete the storage pool from the cockpit GUI.
2] Even in general, there is no option to delete storage-pool from the cockpit GUI after creating it.
3] This can be done from the virt-manager.
Connection --> Details --> Storage --> Stop pool --> Delete pool (icons)
Version-Release number of selected component (if applicable):
RHEL 8 Beta
cockpit-dashboard-183-1.el8.noarch
cockpit-storaged-183-1.el8.noarch
cockpit-183-1.el8.x86_64
How reproducible:
Always
Steps to Reproduce:
1. From the tab "Virtual Machines" --> "Storage Pools"
2. Create a storage pool
3. There is no option to stop or delete it.
Actual results:
Unable to delete pool.
Expected results:
Ability to stop and delete the storage pool just like in virt-manager.
Additional info:
Created attachment 1513862[details]
cockpit
OK, autostart is available when the host boots but we are still missing on stop and remove storage pool options.
Test Versions:
cockpit-machines-193-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64
Test Steps:
1. Create a storage pool through page
2. Click the 'Deactivate' button of the storage pool, and make sure with command which is 'virsh pool-info ${poolname}'.
3. Click the 'Activate' button of the storage pool, and make sure with command which is 'virsh pool-info ${poolname}'.
4. Click the 'Delete' button of the storage pool, and make sure with command which is 'virsh pool-list --all'.
Test Results:
The storage pool can be deactivated/activated/deleted from the page, and the results of command are correct.
According to the results, the storage pool can be deactivated/activated/deleted.So move the status to 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