Upon calling create Volume Group a few checks are done.
One of the check is Volume Group name collision.
This could be valid (duplicate name, pre-seed mistake, etc) or it could be a "zombie" Volume Group that got detected on otherwise empty partition.
There is a codepath to remove existing volume groups with confirmation.
I think instead claiming name collision, we should take that path:
- it can be pre-seeded out
- user can proceed to remove "zombie"/name-conflict or back out to partitioning
Upon calling create Volume Group a few checks are done. /name-conflict or back out to partitioning
One of the check is Volume Group name collision.
This could be valid (duplicate name, pre-seed mistake, etc) or it could be a "zombie" Volume Group that got detected on otherwise empty partition.
There is a codepath to remove existing volume groups with confirmation.
I think instead claiming name collision, we should take that path:
- it can be pre-seeded out
- user can proceed to remove "zombie"
I will try to patch this & test it.
Does this sound reasonable?