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 1668882 - [machines] Cannot delete storage volumes that are in the storage pools.
Summary: [machines] Cannot delete storage volumes that are in the storage pools.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: 8.1
Assignee: Katerina Koukiou
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On: 1678935
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-23 19:43 UTC by Bimal Chollera
Modified: 2020-11-14 12:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:41:35 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 Knowledge Base (Solution) 3922431 0 None None None 2019-02-19 07:47:18 UTC
Red Hat Product Errata RHBA-2019:3325 0 None None None 2019-11-05 20:41:46 UTC

Description Bimal Chollera 2019-01-23 19:43:58 UTC
Description of problem:

From the cockpit UI - Virtual Machines -> Storage Pools -> Storage Volumes.
There is no option to delete a volume.


Version-Release number of selected component (if applicable):

cockpit-system-184-1.el8.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Martin Pitt 2019-01-29 10:58:46 UTC
This is being worked on in https://github.com/cockpit-project/cockpit/pull/10944

Comment 2 Martin Pitt 2019-02-12 20:23:09 UTC
This landed in upstream release 187, thus on track for RHEL 8.1.

Comment 5 YunmingYang 2019-05-29 06:55:41 UTC
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 the page, and create a volume by command which is 'virsh vol-create-as ${poolname} ${volname} --capacity 50M --format qcow2'
2.Refresh the pool by command which is 'virsh pool-refresh ${poolname}', and check the volume on the page.
3.check the checkbox of the new volume through and click 'Delete 1 volume' button
4.Make sure with command which is 'virsh vol-list default'

Test Results:
The volume can be deleted through page


According to the results, the volume can be deleted through page.So move the status to VERIFIED.

Comment 7 errata-xmlrpc 2019-11-05 20:41:35 UTC
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


Note You need to log in before you can comment on or make changes to this bug.