Somewhat expected (but we wanted to see it for real) is an autopkgtest in Chrony that fails since some past update to iproute (or earlier).
Example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/c/chrony/20190717_081612_33487@/log.gz
The error is: time-sources-from-dhcp-servers FAIL stderr: md5sum: /run/systemd/resolved.conf.d/isc-dhcp-v4-dummy0.conf: No such file or directory
It is uncritical for the test, but it triggers on stderr being present.
Somewhat expected (but we wanted to see it for real) is an autopkgtest in Chrony that fails since some past update to iproute (or earlier).
Example: /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- eoan/eoan/ amd64/c/ chrony/ 20190717_ 081612_ 33487@/ log.gz
https:/
The error is: from-dhcp- servers FAIL stderr: md5sum: /run/systemd/ resolved. conf.d/ isc-dhcp- v4-dummy0. conf: No such file or directory
time-sources-
It is uncritical for the test, but it triggers on stderr being present.