Public bug reported: [ Impact ]
Cloud-init handles 503's generically as any other errors even though it is a message from the server of when and how to retry later. This is issues within AWS. [ Test Plan ] Boot an instance. Observe a 503 from the IMDS when contacting the metadata service. Ensure the request is eventually retried and succeeds. [ Where problems could occur ] This required a somewhat hefty refactor, this there is a bit more risk to this one. If there was a bug introduced here it could lead to failure to obtain metadata and inability for an instance to fully come up. That said, the suite of integration tests will detect such a problem for the vast majority of use cases. [ Other info ] Upstream issue: https://github.com/canonical/cloud-init/issues/5577 Upstream PR: https://github.com/canonical/cloud-init/pull/5938 ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Noble) Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
