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.

Created attachment 1178324 [details]
Error message picture

Description of problem:
Error message prompts when removing the physical volume from the volume group.

Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160708.0.x86_64
imgbased-0.7.2-0.1.el7ev.noarch
cockpit-0.108-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Interactive install redhat-virtualization-host-4.0-20160708.0.x86_64 with kickstart file in attachment
    Using part disk manually, and make some disk spaces not parted.
2. Login cockpit website hostIP:9090 with root account
3. Select the disk in cockpit storage page, and create 2 or more partition.
4. Create PVs using the partition in steps 3 on host console.
5. In cockpit, add volume group with PVs in Steps 4
6. Select the added volume group to list the physical volumes
7. Click remove button for every physical volume

Actual results:
Error message prompts when removing the physical volume from the volume group.

Expected results:
All the physical volumes can be removed successfully

Additional info: 
When removing the last physical volume(2 PVs for the VG), the bug occurs.

Created attachment 1178325 [details]
ks file

Created attachment 1178326 [details]
log files

Did the action succeed?
If not the problem is with the failure and not with the UI.

Doron,
After the error message is displayed, click the "Close" button, the physical volume cannot removed successfully. It still be there.

This looks like a cockpit issue, moving it over.

Apparently the volume group can't be empty.

We can either disable the remove button for the last device or offer to delete the entire group. What is the desired behavior here?

Note that the same thing happens when trying to delete the last disk from a RAID.

We should disable the "Remove" button with a tooltip describing the reason.

Here is a PR with a different approach: https://github.com/cockpit-project/cockpit/pull/4822

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://rhn.redhat.com/errata/RHBA-2016-2624.html