mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-11-18 18:16:02 +01:00
Holding dispatch in the drainer cannot help an orchestration that is already running when salt-master restarts: its first action raises, and the next action's refresh_pillar is published seconds after the restart, before minions have rejoined the publisher, so it fails with "No minions responded". refresh_pillar now retries (3 attempts, 10s apart; a failed attempt takes about 15s to time out, so the later attempts land after the reconnect window). It also runs ahead of highstate actions, which now require it, so they get the same reachability check. Retrying the highstate step itself is not an option because it would re-run a fleetwide highstate whenever any state failed. Run straight after a salt-master restart on a standalone 3.5.0 install, the orchestration previously failed with "No minions responded"; it now succeeds on the second attempt. A target that is genuinely offline takes about 65s to fail instead of 15s.