Well, I was wrong: the problem still exists exactly as described in the bug description. To summarize:
- Once a vg is deleted, a vg with the same name can't be created.
- If a partition that used to be in a deleted vg is reused, say /dev/vda3, the installation fails with error: "/dev/vda3 is apparently in use by the system; will not make a filesystem here!" while trying to format the partition.
- This is because the vg doesn't really get deleted: /dev/mapper/vg0-lv--0 is still there and lvmdiskscan lists /dev/vda3 as part of a LVM volume.
Well, I was wrong: the problem still exists exactly as described in the bug description. To summarize:
- Once a vg is deleted, a vg with the same name can't be created. vg0-lv- -0 is still there and lvmdiskscan lists /dev/vda3 as part of a LVM volume.
- If a partition that used to be in a deleted vg is reused, say /dev/vda3, the installation fails with error: "/dev/vda3 is apparently in use by the system; will not make a filesystem here!" while trying to format the partition.
- This is because the vg doesn't really get deleted: /dev/mapper/