> 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
On May 1, 2025 01:21, Jeremy Stanley 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
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
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
