Files
securityonion/salt
Josh Patterson 65816ae717 FIX: hold push dispatch while salt-master has only just started
A push dispatched seconds after a salt-master restart was lost: minions
rejoin the new publisher on a randomized ZeroMQ reconnect delay (up to
~22s with the default recon_default/recon_max), and a job published
before then reaches nobody. The orchestration's refresh_pillar step timed
out with "No minions responded", the drainer logged "push failed" as an
ERROR, and so-log-check failed the run.

Seen on a standalone 3.5.0 install: a highstate restarted salt-master
(new reactor/engine config), the drainer dispatched a soc push 8s later,
and the job cache shows the refresh_pillar job matched the minion but got
no return. Measured on the same host over five restarts, jobs published
in the first 4-9s were lost every time.

The drainer now leaves ready intents in place for a later pass while
/var/run/salt-master.pid is less than 45s old. On a multi-node grid this
also avoids a batch state run silently skipping the minions that have
not reconnected yet, since batch only sends the job to minions that
answer its ping.
2026-11-18 10:27:34 -05:00
..
2025-12-02 11:16:08 -06:00
…
2026-11-10 17:30:01 -06:00
2026-11-10 17:30:01 -06:00
2024-07-09 10:06:16 -04:00
2026-11-16 13:52:05 -06:00
2026-10-05 17:43:08 -04:00
2026-03-19 14:39:10 -04:00
2026-10-02 12:03:04 -04:00
2026-01-07 14:14:57 -05:00
2025-10-14 11:03:00 -04:00
2025-08-04 15:25:26 -04:00