simp-core's default suite has an extensive rsyslog integration test for local logging and log forwarding. In lieu of testing with mock log events via logger (as is done in pupmod-simp-rsyslog and pupmod-simp-simp_rsyslog), this test stimulates events that generate log messages from actual applications (e.g., puppetserver error logs). Unfortunately, due to rsyslog itself, the rsyslog forwarding verifications have proven to be unreliable. As a stopgap measure, the tests were modified to skip any rsyslog test that fails in the simp-core default suite, in lieu of failing. Unfortunately, this has the potential to hide actual problems. So this ticket is to verify that all the checks executed in this test actually work.
One rsyslog forwarding failed to forward, (sudo entry in secure), and because the local log was turned off because the host was also the forwarding log server, no local log existed as well.
Although we could configure the log server to also log to its local log, that doubling of log space is undesirable. has indicated this is not an issue we should address at this time.