Comment 3 for bug 133905

Okay, I'd like to add additional information then. If you activate a VG with the same name as an existing VG, as far as I can tell, none of the user space tools can differentiate between the two. Since people tend to name VGs the same between systems (vg0, VolGroup0), simply removing a drive from one LVM system and putting it into another is enough to get you into this situation.

I would agree to close this bug if conflictingly named VGs were not activated by default. Or at all, until somebody changes the name.