** Attachment added: "Output of networkd-test.py"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759255/+files/networkd-test.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
** Attachment added: "Journal of systemd while running the test"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759257/+files/systemd.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Attachment added: "Log of the DNS resolving dnsmasq while running the test"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2058743/+attachment/5759256/+files/dnsmasq-vpn.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Could you please provide journalctl debug logs from systemd-resolved, so
we can get more details of what's going on?
e.g. put this into the systemd-resolved override.conf
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
$ sudo systemctl edit systemd-resolved
$ sudo systemctl restart
It appears most of the systemd autopkgtest failures are because of this
flaky test:
https://autopkgtest.ubuntu.com/packages/systemd/jammy/amd64
The effort required to manually retrigger systemd autopkgtests because
of that flaky test is substantial. We should disable that particular
test unless
Sounds like some interaction issue between the system, systemd, and
dnsmasq somehow. As this fails on and off since a very long time. When I
test with the older dnsmasq and getting a success the time spent on the
test seems overly long. Like there is something not quite right even
then.
** Also
The same issue was present with the old dnsmasq package...for example:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/s/systemd/20240224_133847_88f29@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
7 matches
Mail list logo
