I can now confirm that the bug has been introduced strictly by the glibc 2.34, and not another package in the -proposed pocket.
My reproduction steps were as following: Boot an Ubuntu Impish qemu VM (fully up-to-date (funnily enough, far from being a trivial thing to do, see at the bottom for pointers). In the VM, install the dpkg-dev and dnsmasq-base packages, get the systemd sources, go into the test subdirectory of the sources, and run the following command: sudo python3 networkd-test.py DnsmasqClientTest.test_coldplug_dhcp_ip6 It should succeed (it has, in my case). Then enable the -proposed pocket in the APT sources, with APT preferences looking like so Package: * Pin: release a=impish-proposed Pin-Priority: 50 Finally, update *only* the glibc: sudo apt install -t impish-proposed libc6 Reboot the VM, go into the test directory, and run the same python3 command as above. It now fails. To revert to the previous state of the VM (if you haven't made a snapshot), simply use an apt preference > 1000 for the a=impish packages, the resolver will downgrade every package. I captured straces for both debug runs for the networkd daemon, I'll attach them to the post. For reference, to get them, I changed the ExecStart line in /lib/systemd/system/systemd-networkd.service to ExecStart=sh -c "strace -o /tmp/networkd.strace -p $$$$ & exec /lib/systemd/systemd-networkd" , added this line ReadWritePaths=/tmp and added CAP_SYS_PTRACE to the AmbiantCapabilties and CapabilitiesBoundingSet lines. How I finally managed to get a VM up and running: * used `autopkgtest-buildvm-ubuntu-cloud -v -r impish --arch armhf` using autopkgtest git master -> This gave me an image with credentials and disk space * Used `mount-image-callback my.img --mountpoint /mnt -- cp -L /mnt/boot/vmlinuz /mnt/boot/initrd.img` to extract the kernel and initrd -> couldn't figure out how to use a proper bootloader, so direct kernel boot * use virtio for the img, and add root=/dev/vda1 as a kernel argument when launching qemu. ** Attachment added: "networkd-glib-2.33.trace" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+attachment/5520980/+files/networkd-glib-2.33.trace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1940635 Title: systemd-networkd failing to acquire a DHCP6 lease from dnsmasq on armhf Status in glibc package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: systemd-networkd is failing to acquire a DCHP6 lease from dnsmasq on armhf since glibc 2.34-0ubuntu1, failing systemd (tests-name=networkd- test.py) and netplan.io (test-name=ethernets) tests on armhf. Reproducer: * Setup an armhf container, e.g. via: autopkgtest systemd --test-name=networkd-test.py --shell -U --apt-pocket=proposed=src:systemd,src:glibc -s -- lxd autopkgtest/ubuntu/impish/armhf * It will fail and drop you into the shell * cd test/ && apt install python3-nose * nosetests3 -v -s -m "test_.*_dhcp_ip6" networkd-test.py This is unrelated to the recent dnsmasq changes (LP: #1894619), as that would fail on all architectures, not just armhf. It still passes inside an amd64 LXD container, so it is also not related to armhf being tested inside a container. But it shows the difference between armhf vs amd64 container, that on armhf we're missing the DHCPSOLICIT (and therefore DHCPREPLY) messages, as can be seen from the dnsmasq log: dnsmasq-dhcp[]: DHCPSOLICIT(router_eth42) 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 dnsmasq-dhcp[]: DHCPREPLY(router_eth42) 2600::1f 00:02:00:00:ab:11:57:1e:20:2f:9e:56:5f:34 autopkgtest-lxd-rtypaf The issue is most probably the same that causes the currently failing netplan.io/ethernets autopkgtest on armhf, if tested against glibc 2.34-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1940635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
