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 co
> Since it sounds like you're experiencing this in an OpenStack cloud,
> one workaround would be to boot your server instance with
> configdrive enabled; cloud-init knows how to get its metadata that
> way as well.
Dear Jeremy,
Thank you for your response and the suggestion to enable configdrive
root@localhost:/home/debian# cat /etc/netplan/50-cloud-init.yaml
network:
version: 2
ethernets:
enp3s0:
match:
macaddress: "fa:16:3e:b3:91:7c"
dhcp4: true
dhcp6: true
set-name: "enp3s0"
root@localhost:/home/debian# ip a
1: lo: mtu 65536 qdisc noqueue state U
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 met
Package: cloud-init
Subject: cloud-init fails to handle IPv6-only environments in Debian 12
generic-cloud
Dear Debian Development Team,
I am writing to report an issue with the cloud-init package in the current
version of Debian 12 (Bookworm). In an IPv6-only environment, cloud-init
fails to pro
