So what happens if you get a 503, we now ignore it, but at the same time didn't get the configuration data we need for the instance, and boot nevertheless. We will be booting an unconfigured instance, right? Or will cloud-init remain in the background retrying, and eventually (hopefully) succeed, and then configure the instance?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2094858 Title: Cloud-init fails on AWS if IMDSv2 returns a 503 error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2094858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
