Bug#1108403: (no subject)
On Jun 28, 2025 14:59, Jeremy Stanley <fungi@yuggoth.org> wrote:
>
> On 2025-06-28 09:47:36 +0200 (+0200), Bastian Blank wrote:
> [...]
> > How that? Most parts of cloud-init are one shot, including the user
> > setup.
>
> If the VM gets its network configuration from metadata instead of
> DHCP/SLAAC+RA and isn't relying on configdrive and isn't falling
> back to using network settings cached into /etc from a prior boot
> (and is running on a non-amd64 arch), then it can come up with no
> reachable network. That combination of factors should be
> exceptionally rare however.
>
> The more likely scenario, you're right, is that updated images fail
> when trying to create and boot a new VM from them for the first
> time, but that's probably far less problematic since users can
> typically roll back to an older version of the image or adjust their
> options to e.g. turn on configdrive when available.
> --
> Jeremy Stanley
FYI, I expect most OpenStack operators to configure a config drive by default, as it is the most reliable metadata source.
Thomas Goirand
Reply to: