I just got hit by this bug too. On a fully patched Ubuntu Server 10.04.4 LTS box, I used vgimportclone and it renamed a different volume group than I asked it to, leaving me with an unbootable system until I was able to rename the volume group back.
I just got hit by this bug too. On a fully patched Ubuntu Server 10.04.4 LTS box, I used vgimportclone and it renamed a different volume group than I asked it to, leaving me with an unbootable system until I was able to rename the volume group back.