Skip to content

Fix #68915: Syndic reconnect after Master of Masters restart - #68923

Open
MuraveyApp wants to merge 2 commits into
saltstack:3007.xfrom
MuraveyApp:fix/68915-syndic-reconnect
Open

Fix #68915: Syndic reconnect after Master of Masters restart#68923
MuraveyApp wants to merge 2 commits into
saltstack:3007.xfrom
MuraveyApp:fix/68915-syndic-reconnect

Conversation

@MuraveyApp

Copy link
Copy Markdown

Summary

  • Fixes syndic failing to reconnect after MoM restart with ZeroMQ
    Generated by OwlMind

@twangboy

Copy link
Copy Markdown
Contributor

Please remove the owlmind file. Needs a changelog and tests

@dwoz
dwoz force-pushed the fix/68915-syndic-reconnect branch from 30f188b to 9ad5eed Compare June 26, 2026 13:18
@dwoz dwoz added this to the Potassium v3009.0 milestone Jun 26, 2026
@dwoz
dwoz changed the base branch from master to 3007.x July 4, 2026 01:04
dwoz added 2 commits July 3, 2026 18:05
- Invalidate auth on pub_channel before close in Syndic.reconnect() so
  stale tokens are not reused on reconnection.
- Start ZeroMQSocketMonitor on PublishClient.connect() with a
  reconnect_callback; on subsequent EVENT_CONNECTED events (after initial
  connection), the callback is scheduled via asyncio.ensure_future to
  trigger full re-authentication.
- Add unit tests for ZeroMQSocketMonitor.monitor_callback reconnect
  behaviour and for Syndic.reconnect() auth invalidation.
- Add changelog entry.
Regression test for saltstack#68915. Verifies that a syndic re-establishes
its ZeroMQ connection to the Master of Masters after the MoM
process is restarted, and that job dispatch to downstream minions
through the syndic remains functional after the reconnect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test:full Run the full test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants