+++ This bug was initially created as a clone of Bug #677915 +++
The following was filed automatically by anaconda:
anaconda 13.21.82 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/devices.py", line 2058, in _addLogVol
raise DeviceError("new lv is too large to fit in free space", self.name)
File "/usr/lib/anaconda/storage/devices.py", line 2258, in __init__
File "/usr/lib/anaconda/storage/__init__.py", line 777, in newLV
return LVMLogicalVolumeDevice(name, vg, *args, **kwargs)
File "/usr/lib/anaconda/kickstart.py", line 516, in execute
File "/usr/lib/anaconda/kickstart.py", line 1149, in execute
File "/usr/bin/anaconda", line 1102, in <module>
DeviceError: ('new lv is too large to fit in free space', 'sysvg1')
--- Additional comment from firstname.lastname@example.org on 2011-03-01 22:50:44 EST ---
We added code to storage.devices.LVMVolumeGroupDevice._addLogVol for the special case of a VG whose PVs' sizes are not yet determined due to growable partition requests. Evidently we need to beef that up. It currently only handles PVs that are growable partitions -- it needs to handle PVs that are on any device comprised of or built on growable partitions.
Fixed for Fedora 15 in anaconda-15.22-1.
anaconda-15.22-1.fc15 has been submitted as an update for Fedora 15.
Discussed at 2011-03-11 blocker review meeting. This issue is fixed and available for testing in anaconda-15.22-1. The issue has been accepted as a beta blocker.
anaconda-15.22-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.