Red Hat Bugzilla – Bug 137054
Exceed max PVs in an LV: undefined errorMessage
Last modified: 2009-04-16 19:10:13 EDT
Description of problem:
Create a new VG with Maximum Physical Volumes of 1. Select an
Unallocated Volume, click Add to existing Volume Group, select the VG
you just created and click Add. The GUI remains at the "Add Physical
Volume to VG"; no apparent error from this perspective.
On the command line you get the traceback:
No space for '/dev/sdd1' - volume group '1PV' holds max 1 physical
Unable to add physical volume '/dev/sdd1' to volume group '1PV'.
Traceback (most recent call last):
File "/usr/share/system-config-lvm/InputController.py", line 810, in
NameError: global name 'errorMessage' is not defined
It would be nice if the first line (or two) of this were returned to
the user in an Error dialog.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This is fixed in 0.9.8-1.0, by informing user that the max number of
PVs or LVs has been allocated, and that no more are allowed. Down the
road, a better way would be to not allow buttons and/or tree elements
associated with VGs that have maxed out from being sensitive to
selection, but this will work great for now (and, perhaps, is more
informative as to why the operation is not possible).
Verified in system-config-lvm-0.9.8-1.0.
"The number of Physical Volumes in this Volume Group has reached its