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.

+++ This bug was initially created as a clone of Bug #1026466 +++

Description of problem:
Existing LVM configurations detected by blivet show existing VGs as having their full capacity available in spite of any existing LVs. This is due to a regression introduced when fixing bug 1013800.

Version-Release number of selected component (if applicable):
python-blivet-0.23.3-1

How reproducible:
Always

Steps to Reproduce:
1. create an anaconda automatic partitioning layout (write it to disk)
2. reboot into the installer using the same disk(s)
3. in the custom storage spoke, create a new LV

Actual results:
A new LV will be added with up to the full size of the VG even though the VG is already full.

Expected results:
Creation of a new LV should fail due to the disk(s) and VG being full.

Additional info:

--- Additional comment from David Lehman on 2013-11-04 12:47:41 EST ---

I have a patch for this and have verified that it fixes this problem.

To be clear, this bug circumvents all checking done by the installer related to accounting for free space within a preexisting VG. That means, for example, that a user would be allowed to add a 100GB LV to an existing 200GB VG that has no free space.

Reproduced with python-blivet-0.18.9-1.el7, verified with python-blivet-0.18.11-1.el7

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.