Thank you for your response. As requested, I tested the latest daily Trixie (Debian 13) cloud image from https://cloud.debian.org/images/cloud/trixie/daily/.
Unfortunately, the same issue persists — cloud-init still fails to properly fetch metadata in an IPv6-only environment, even though the metadata service is reachable via IPv6 using `curl -6`. This suggests that the root cause is not resolved in the current `cloud-init` version shipped with Debian 13 daily images. It appears that cloud-init does not fully handle link-local IPv6 addresses with the interface scope (e.g., `%eth0`), or fails to prioritize IPv6 when no IPv4 is present. This is especially problematic in modern cloud deployments where IPv6-only networking is common. Would you like a new bug report for Debian 13 (Trixie), or should we continue tracking the issue under this report? Please let me know how I can assist further in debugging or reproducing the issue. Best regards
