We *really* need to get the curtin commit hash into curtin/__init__.py or curtin/version.py:_PACKAGED_VERSION so we know exactly what curtin is running since we're picking by hash.
That said, this looks strange to me, I didn't think subiquity set that recently...
'/dev/sda', 'wipe': 'superblock-recursive'
Looking at the wiping of sda, we now check if the device to be wiped is a multipath member and skip it. sda is a member, and the output does not show that curtin ran the multipath -c command before wiping ... it *looks* to me that this build did not include the fix for this scenario.
We *really* need to get the curtin commit hash into curtin/__init__.py or curtin/ version. py:_PACKAGED_ VERSION so we know exactly what curtin is running since we're picking by hash.
That said, this looks strange to me, I didn't think subiquity set that recently...
'/dev/sda', 'wipe': 'superblock- recursive'
Looking at the wiping of sda, we now check if the device to be wiped is a multipath member and skip it. sda is a member, and the output does not show that curtin ran the multipath -c command before wiping ... it *looks* to me that this build did not include the fix for this scenario.