Bug#1104426:

To: 1104426@bugs.debian.org
Subject: Bug#1104426:
From: Jeremy Stanley <fungi@yuggoth.org>
Date: Wed, 30 Apr 2025 16:56:16 +0000
Message-id: <[🔎] aBJWMJZqlMfw5Cko@yuggoth.org>
Reply-to: Jeremy Stanley <fungi@yuggoth.org>, 1104426@bugs.debian.org
In-reply-to: <[🔎] CAHZwAWF3F8-7pWGt08HVn2bKd8U7Df8VJYJqYPUk330T8TxDFw@mail.gmail.com>
References: <[🔎] CAHZwAWHs6MPiwLN55zTib9VbBMhxVX0-yks9DusH5oX8aGzDZw@mail.gmail.com> <[🔎] CAHZwAWF3F8-7pWGt08HVn2bKd8U7Df8VJYJqYPUk330T8TxDFw@mail.gmail.com> <[🔎] CAHZwAWHs6MPiwLN55zTib9VbBMhxVX0-yks9DusH5oX8aGzDZw@mail.gmail.com>

Since it sounds like you're experiencing this in an OpenStack cloud,one workaround would be to boot your server instance withconfigdrive enabled; cloud-init knows how to get its metadata thatway as well.

--
Jeremy Stanley

Reply to:

References:
- Bug#1104426: cloud-init fails to handle IPv6-only environments in Debian 12 generic-cloud
  - From: Zar VPN <zarnet.co@gmail.com>
- Bug#1104426:
  - From: Zar VPN <zarnet.co@gmail.com>

Prev by Date: Bug#1104426: Collected Logs
Previous by thread: Bug#1104426:
Next by thread: Bug#1104426: Collected Logs
Index(es):
- Date
- Thread