Would you be able to run cloud-init collect-logs and attach the tarball it creates?
Alternatively, if you could provide a sanitized version of /var/log/cloud-init.log; that should be sufficient to see what's going on.
Lastly, when creating a new instance with captured disks, shouldn't cloud-init find a new ovf-xml from the attached iso versus loading the previously saved xml file? Otherwise, this would set the created user's password to the redacted value rather than the original password when you created the first instance?
Thanks for filing the bug.
Would you be able to run cloud-init collect-logs and attach the tarball it creates?
Alternatively, if you could provide a sanitized version of /var/log/ cloud-init. log; that should be sufficient to see what's going on.
Lastly, when creating a new instance with captured disks, shouldn't cloud-init find a new ovf-xml from the attached iso versus loading the previously saved xml file? Otherwise, this would set the created user's password to the redacted value rather than the original password when you created the first instance?