One can make these things unambiguous.
curtin could generate a uuid on the fly, and then pass vg_uuid to all the commands it uses.
or we could start making slightly more unique vg names, i.e. ubuntu-vg-3a185.
I'm not sure what's best.
Indeed this is a long standing issue we have been observing with d-i, ubiquity, curtin, subiquity =)
Even mounting backup of one Ubuntu system, on another leads to similar confusions.
One can make these things unambiguous.
curtin could generate a uuid on the fly, and then pass vg_uuid to all the commands it uses.
or we could start making slightly more unique vg names, i.e. ubuntu-vg-3a185.
I'm not sure what's best.
Indeed this is a long standing issue we have been observing with d-i, ubiquity, curtin, subiquity =)
Even mounting backup of one Ubuntu system, on another leads to similar confusions.