Bug#1104426:

To: 1104426@bugs.debian.org
Subject: Bug#1104426:
From: thomas@goirand.fr
Date: Thu, 01 May 2025 12:11:45 +0800
Message-id: <[🔎] ee0ade4e-166a-4444-8426-17bd3e5bb5d8@goirand.fr>
Reply-to: thomas@goirand.fr, 1104426@bugs.debian.org
In-reply-to: <aBJWMJZqlMfw5Cko@yuggoth.org>
References: <CAHZwAWHs6MPiwLN55zTib9VbBMhxVX0-yks9DusH5oX8aGzDZw@mail.gmail.com> <CAHZwAWF3F8-7pWGt08HVn2bKd8U7Df8VJYJqYPUk330T8TxDFw@mail.gmail.com> <CAHZwAWHs6MPiwLN55zTib9VbBMhxVX0-yks9DusH5oX8aGzDZw@mail.gmail.com> <aBJWMJZqlMfw5Cko@yuggoth.org> <CAHZwAWHs6MPiwLN55zTib9VbBMhxVX0-yks9DusH5oX8aGzDZw@mail.gmail.com>

On May 1, 2025 01:21, Jeremy Stanley <fungi@yuggoth.org> wrote:

> 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.

> --

> Jeremy Stanley

Correct, however, this is still an issue in the Debian image that deserves a fix.

Thomas Goirand (zigo)

Reply to: