[BUG] Multiple hot masters configuration does not work as expected
@dwoz is already working on this.
Since Oct 12, 2021.
- Dominant language
- Python
- Stars
- 15.7k
- Forks
- 5.6k
- Avg merge
- 2d 44m
- Merged PRs (30d)
- 80
Description
Description
When configuring a minion in a redundant master setup, where all masters are "hot", the job returns are only sent to the master that issued the command, rather than all.
Setup
Install salt-master on two separate machines. Copy the master.pem and master.pub from one machine to the other so that they have the same keys.
Install salt-minion on a separate machine and configure as follows
master:
- <salt-master-0-ip>
- <salt-master-1-ip>
master_type: str
Where <salt-master-0-ip> and <salt-master-1-ip> are the master's ip addresses, respectively.
Steps to Reproduce the behavior
Run a job from salt-master-0
salt \* test.ping --async
Observe the return using a runner
salt-run jobs.lookup_jid <jid>
Where <jid> is the jid returned from the prior command
Observe that you cannot see return from other master
salt-run jobs.lookup_jid <jid>
Expected behavior
I expected the job data to be returned to both masters since they are configured as "hot-hot". Not returning jobs to both masters reduces the utility of this configuration
Versions Report
Salt Version:
Salt: 3003.2
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: Not Installed
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 2.11.1
libgit2: Not Installed
M2Crypto: 0.35.2
Mako: Not Installed
msgpack: 0.6.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: Not Installed
pygit2: Not Installed
Python: 3.6.8 (default, Nov 16 2020, 16:55:22)
python-gnupg: Not Installed
PyYAML: 3.13
PyZMQ: 17.0.0
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.1.4
System Versions:
dist: centos 7 Core
locale: UTF-8
machine: x86_64
release: 3.10.0-1127.el7.x86_64
system: Linux
version: CentOS Linux 7 Core
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.
Assessment
This issue has not been assessed yet.