Comment 3 for bug 1783413

OK, I've taken this configuration and recreated the issue with our vmtest; we create the storage config, then tear down the lvm and raid (removing configurations from /etc/lvm and /etc/mdadm) then run the storage config a second time. We see the same storage tree (missing the lvm dm0 entries) and then trigger the vgcreate error where vg0 already exists).

The fix is for curtin to add an lvm scan of block devices after assembling raid arrays; This scan will enable any lvm vgs that can be assembled. Then once curtin can "see" the lvm devices, it will properly remove them.