On Sun, May 04, 2025 at 08:05:00AM +0200, Bastian Blank wrote:
> On Sat, May 03, 2025 at 10:57:39PM -0400, Noah Meyerhans wrote:
> > There shouldn't be any name resolution involved here at all. My guess
> > is that something is not recognizing the scoped link-local address as an
> > IP address, an
On Sat, May 03, 2025 at 10:57:39PM -0400, Noah Meyerhans wrote:
> There shouldn't be any name resolution involved here at all. My guess
> is that something is not recognizing the scoped link-local address as an
> IP address, and is treating it as a hostname that needs to be resolved
> in DNS. Whi
Control: tags -1 + upstream
Control: forwarded -1 https://github.com/canonical/cloud-init/issues/6205
On Sat, May 03, 2025 at 12:25:01PM +0330, Zar VPN wrote:
>This is a critical issue, as it prevents users from booting and
>configuring instances in modern IPv6-only cloud environments usin
Processing control commands:
> tags -1 + upstream
Bug #1104426 [cloud-init] cloud-init fails to handle IPv6-only environments in
Debian 12 generic-cloud
Added tag(s) upstream.
> forwarded -1 https://github.com/canonical/cloud-init/issues/6205
Bug #1104426 [cloud-init] cloud-init fails to handle I
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
