Oh, a final question. Is the imds service the only way an instance can get its configuration? Would there be a scenario where cloud-init would be getting its config via something else, but still reach out to the metadata service, and halt boot if the metadata service is ill even though it could already be getting its config via that other method? In other words, we would be in that retry loop for no reason, since we got the config via that other method.
-- 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
