[DOCS] 3008.x - Master Cluster Configuration Requires Interface Setting
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Start with the Master Cluster Documentation and the referenced salt/cluster/consensus/service.py lines 79-83 to confirm how the interface setting affects peer communication. Update the master cluster documentation to state that interface must be set in the master configuration, and verify that the requirement and its purpose are clear.
Written by the indexing model from the issue text.
Description
Description
If the master configuration on a cluster peer does not have the interface IP set, the default of 0.0.0.0 will be used. This will cause raft communication to not function between peers and errors like this will show up in /var/log/salt/master:
2026-07-19 08:21:19,024 [salt.cluster.consensus.peer:327 ][WARNING ][2460] RaftDispatcher: no pusher for 0.0.0.0, dropping cluster/raft/pre-request-vote-reply reply
This comment confirms the configuration requirement:
Suggested Fix
Add documentation indicating that interface must be set in the master configuration for peer communication to work in a master cluster.
Type of documentation
Salt documentation
Location or format of documentation
Master Cluster Documentation
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from saltstack/salt
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
# [BUG] deltaproxy: sub-proxy init failures are logged at INFO and invisible at default log level Openbug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100