Description of problem:
I noticed there is code for checking duplicate VG naming and that it
was not catching duplicate names. Did a little debugging on this:
ok_new_vg() calls query_VGs() to get the existing Volume Groups.
query_VGs() gets output in this format:
splits on commas and puts words 0, 4, and 5 in a structure. Back in
ok_new_vg it's then comparing "VG1" to " VG1" and not matching.
Stripping whitespace in query_VGs should remedy this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Looks like the same thing exists in the following procedures with
potential for other problems:
could use 'name = words.strip()'
Fixed in 0.9.4-1.0
Verified in system-config-lvm-0.9.6-1.0:
"A Logical Volume with the name HOMER already exists in this Volume
Group. Please choose a unique name."