"test_rsyslog (__main__.ServicesTest) ... FAIL" due to syslog forwarding being broken #14799
Description
git master (1294661)
When trying to run the autopkgtest (via qemu) I get the following failure in boot-and-services
======================================================================
FAIL: test_rsyslog (__main__.ServicesTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/tmp/autopkgtest.se4fqU/build.yQc/src/debian/tests/boot-and-services", line 116, in test_rsyslog
self.assertRegex(log, 'NetworkManager.*:')
AssertionError: Regex didn't match: 'NetworkManager.*:' not found in <snip>
Looging into the qemu instance, rsyslog and journald seem to be running fine:
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2020-02-06 02:39:15 UTC; 12min ago
TriggeredBy: ● syslog.socket
Docs: man:rsyslogd(8)
https://www.rsyslog.com/doc/
Main PID: 299 (rsyslogd)
Tasks: 4 (limit: 1146)
Memory: 2.2M
CGroup: /system.slice/rsyslog.service
└─299 /usr/sbin/rsyslogd -n -iNONE
Feb 06 02:39:15 host systemd[1]: Starting System Logging Service...
Feb 06 02:39:15 host rsyslogd[299]: getaddrinfo failed obtaining local hostname - using 'host' instead; error: No address associated with hostname [v8.2001.0]
Feb 06 02:39:15 host rsyslogd[299]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2001.0]
Feb 06 02:39:15 host rsyslogd[299]: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="299" x-info="https://www.rsyslog.com"] start
Feb 06 02:39:15 host systemd[1]: Started System Logging Service.
● systemd-journald.service - Journal Service
Loaded: loaded (/lib/systemd/system/systemd-journald.service; static; vendor preset: enabled)
Active: active (running) since Thu 2020-02-06 02:39:15 UTC; 12min ago
TriggeredBy: ● systemd-journald-dev-log.socket
● systemd-journald-audit.socket
● systemd-journald.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 182 (systemd-journal)
Status: "Processing requests..."
Tasks: 1 (limit: 1146)
Memory: 16.2M
CGroup: /system.slice/systemd-journald.service
└─182 /lib/systemd/systemd-journald
Feb 06 02:39:15 host systemd-journald[182]: Journal started
Feb 06 02:39:15 host systemd-journald[182]: Runtime Journal (/run/log/journal/3fcaf5b9609d41f3a73e75f622a7e4a3) is 1.2M, max 9.8M, 8.6M free.
Feb 06 02:39:15 host systemd-journald[182]: Time spent on flushing to /var/log/journal/3fcaf5b9609d41f3a73e75f622a7e4a3 is 11.497ms for 534 entries.
Feb 06 02:39:15 host systemd-journald[182]: System Journal (/var/log/journal/3fcaf5b9609d41f3a73e75f622a7e4a3) is 16.0M, max 2.4G, 2.4G free.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
A logger foo is not forwarded to rsyslog though.
Running the same rsyslog package on v244.1 works fine.