debian/sid/cloud VM have broken networking

[simondeziel]

Launching a container with images:debian/sid/cloud works well in the sense that cloud-init does it's job:

lxc launch images:debian/sid/cloud debian-sid-cloud

lxc shell debian-sid-cloud

root@debian-sid-cloud:~# ip a
...
51: eth0@if52: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:16:3e:81:5a:78 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.98.30.19/24 metric 1024 brd 10.98.30.255 scope global dynamic eth0
       valid_lft 3341sec preferred_lft 3341sec
    inet6 fd3:c543:69f7:b184:216:3eff:fe81:5a78/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 3401sec preferred_lft 3401sec
    inet6 fe80::216:3eff:fe81:5a78/64 scope link 
       valid_lft forever preferred_lft forever

root@debian-sid-cloud:~# journalctl -u cloud-init | head
Apr 21 21:19:04 debian-sid-cloud systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: Cloud-init v. 21.4 running 'init' at Thu, 21 Apr 2022 21:19:05 +0000. Up 1.25 seconds.
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: ++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: +--------+------+-----------------------------+-----------+-------+-------------------+
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: | Device |  Up  |           Address           |    Mask   | Scope |     Hw-Address    |
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: +--------+------+-----------------------------+-----------+-------+-------------------+
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: |  eth0  | True | fe80::216:3eff:fe55:3547/64 |     .     |  link | 00:16:3e:55:35:47 |
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: |   lo   | True |          127.0.0.1          | 255.0.0.0 |  host |         .         |
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: |   lo   | True |           ::1/128           |     .     |  host |         .         |
Apr 21 21:19:05 debian-sid-cloud cloud-init[122]: ci-info: +--------+------+-----------------------------+-----------+-------+-------------------+

If one uses a VM instead, cloud-init will fail, apparently due to having enp5s0 down:

lxc launch images:debian/sid/cloud debian-sid-cloud-vm --vm

lxc shell debian-sid-cloud-vm

root@debian-sid-cloud-vm:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:16:3e:e0:39:de brd ff:ff:ff:ff:ff:ff

root@debian-sid-cloud-vm:~# journalctl -u cloud-init | head
Apr 21 21:22:29 debian-sid-cloud-vm systemd[1]: Starting Initial cloud-init job (metadata service crawler)...
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: Cloud-init v. 21.4 running 'init' at Thu, 21 Apr 2022 21:22:29 +0000. Up 3.87 seconds.
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: +++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: | Device |   Up  |  Address  |    Mask   | Scope |     Hw-Address    |
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: | enp5s0 | False |     .     |     .     |   .   | 00:16:3e:f4:74:e3 |
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: |   lo   |  True | 127.0.0.1 | 255.0.0.0 |  host |         .         |
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: |   lo   |  True |  ::1/128  |     .     |  host |         .         |
Apr 21 21:22:29 debian-sid-cloud-vm cloud-init[371]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+

The NIC status/names can be observed while the instance is booting with:

watch -n1 'lxc query /1.0/instances/${instance_name}/state | jq -r ".network" | grep "state\|eth0\|enp5s0"'

Additional information:

$ lxc image list | grep Debian
|           | 75b75ea00f1f | no     | Debian sid amd64 (20220421_16:35)    | x86_64       | CONTAINER       | 109.18MB | Apr 21, 2022 at 9:00pm (UTC)  |
|           | 93b3dfdd65bd | no     | Debian sid amd64 (20220421_16:35)    | x86_64       | VIRTUAL-MACHINE | 408.19MB | Apr 21, 2022 at 7:47pm (UTC)  |

P.S.: I'm not sure if that should be a bug addressed in cloud-init or here.

[stgraber]

@monstermunchkin