Dear all, Thank you to everyone contributing to this discussion.
I would like to gently emphasize that the core issue reported in this bug is the failure of cloud-init to fetch metadata over an IPv6-only network, specifically when using the debian-12-genericcloud-amd64 image. This results in a complete failure to initialize the instance in such environments. While I appreciate the suggestions involving configdrive, However, this is a side topic. The bug here is not about configdrive support, but rather about the inability of cloud-init to function properly over an IPv6-only metadata service — something that is expected to work. This is a critical issue, as it prevents users from booting and configuring instances in modern IPv6-only cloud environments using the official Debian cloud image. I sincerely hope we can refocus on diagnosing and resolving the actual problem. I remain available to provide any technical detail as needed. Warm regards.
