Bug 1668877
Summary: | [machines] Cannot delete storagepools. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Bimal Chollera <bcholler> |
Component: | cockpit-appstream | Assignee: | Katerina Koukiou <kkoukiou> |
Status: | CLOSED ERRATA | QA Contact: | YunmingYang <yunyang> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8.0 | CC: | mpitt, qiyuan, usurse, xchen |
Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
Target Release: | 8.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 20:41:35 UTC | Type: | Feature Request |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1678935 | ||
Bug Blocks: |
Description
Bimal Chollera
2019-01-23 19:15:52 UTC
This is being worked on in https://github.com/cockpit-project/cockpit/pull/10944 Implemented by commit edcfa9933c82756546c78da9d1d6489fb8f1f5d6 Author: Katerina Koukiou <kkoukiou> machines: implement delete operation for storage pools Which is inside release 186. 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 from page 2.Click the Delete button of the storage pool Test Results: 1.The storage pool can be deleted from the page 2.Use command which is 'virsh pool-list --all', the storage pool has been deleted According to the results, the storage pool can be deleted from the page.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 |