mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-11-18 18:16:02 +01:00
so-push-drainer logs "push result unknown" as a WARNING when salt-master restarts while a pushed state run is queued: the orchestration's next publish fails with AuthenticationError, but the minion still runs the queued state. so-log-check matches any line containing "error", so the quoted exception still failed the check. Reproduced on a distributed 3.5.0 grid: a sensoroni push queued behind a 150s state run on the manager, then salt-master was restarted. The orchestration (which runs under salt-minion.service, so it survives the restart) raised AuthenticationError 9s later, the drainer logged the WARNING, and the queued state run completed with 0 failed states. so-log-check --unknown flagged the line. The pattern requires AuthenticationError so an unknown result from any other raised exception, e.g. a bug in a state module, is still reported.