Hi Travis, Thanks for the logs! I can't tell definitively if this is the problem from the logs we collect, but snapd has failed to seed the system, and I know that cloud-init waits for seeding to complete before executing the modules and final stages (in case the seeded snaps are required by the user-specified configuration that is processed in those stages). My guess is that if you examine the state of the system, you'll see that boot is blocked on snapd.seeded.service (or has failed completely, perhaps).
Are you able to check that for me? Once you've done so, please move this bug back to New. (In the meantime, I'll follow up on the snapd seeding issue.) Thanks! Dan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885973 Title: user-data not being run on 20.04 ARM Graviton 2 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
