I'm marking the cloud-init task invalid for now. As mentioned in the other bug[1]; cloud-init is not running too late; rather scripts not provided to cloud-init are not waiting for cloud-init to complete its execution. If your scripts are using cloud-init status --wait before executing or systemd units are gated with After=cloud- init.target, then please re-open this task by marking it New again. When doing so please attach ubuntu-bug cloud-init output and a sample of your scripts and how they're added to the image so we can see when they are running.
I do believe that if you gate your scripts to run after cloud-init has completed there shouldn't be any issues. 1. https://bugs.launchpad.net/subiquity/+bug/1906829/comments/11 ** Changed in: cloud-init (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907107 Title: cloud-init runs too late at first startup after ubuntu autoinstall To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1907107/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
