At the moment, the PTUUID is correct before and after provisioning, but not during. This means that if provisioning is stopped for whatever reason, a user may have to take corrective action to reset or reconfigure to use a new PTUUID, which could be a pain.
This issue comes about because the image, with baked-in partition table, is copied across and then the PTUUID is adjusted to be correct.
A potential solution could be to copy the partition table, with corrected PTUUID, from the image, and then copy the partitions separately, ensuring that the PTUUID remains consistent throughout the operation.
At the moment, the PTUUID is correct before and after provisioning, but not during. This means that if provisioning is stopped for whatever reason, a user may have to take corrective action to reset or reconfigure to use a new PTUUID, which could be a pain.
This issue comes about because the image, with baked-in partition table, is copied across and then the PTUUID is adjusted to be correct.
A potential solution could be to copy the partition table, with corrected PTUUID, from the image, and then copy the partitions separately, ensuring that the PTUUID remains consistent throughout the operation.