Hi Michael, it seems suspicious as it is the same test that fails. But the assertion is different. In the referred Debian bug it is AssertionError: b'megasearch.net: 192.168.42.1' not found in In the Ubuntu fail it is subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1.
Also we did show that 2.86-1 worked fine against systemd 249.7-1ubuntu1 without a change to dnsmasq. Finally the new dnsmasq 2.86-1.1 tested against systemd 249.5-2ubuntu4 here https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20220122_111714_33b38@/log.gz It still shows the same issue as reported here. The referenced error OTOH fails in Debian with 247.9-1 which works for this issue here. So while indeed very close, I doubt it is the same as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995655 Overall I guess eventually we need both fixes anyway, the one in dnsmasq (sync already happened 2.86-1.1 is in j-proposed) and a newer systemd upload. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957086 Title: Autopkgtest systemd fail against dnsmasq 2.86 (22.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
