You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When running jobs against v3006 minions, I can see job returns coming back to both masters.
When running the same job against v3004 minions, the job returns are coming back only to the master that initiated the job.
Setup
Multimaster setup, Active/Active, master version 3004.2
on-prem machine
VM (Virtualbox, KVM, etc. please specify)
VM running on a cloud service, please be explicit and add details
container (Kubernetes, Docker, containerd, etc. please specify)
or a combination, please be explicit
jails if it is FreeBSD
classic packaging
onedir packaging
used bootstrap to install
Steps to Reproduce the behavior
In this environment the minion named host01 is running version 3006.2 while the minion on master01 is running version 3004.2
[user@master01 ~]$ salt -L "host01 master01" test.ping
host01:
True
master01:
True
-------------------------------------------
Summary
-------------------------------------------
# of minions targeted: 2
# of minions returned: 2
# of minions that did not return: 0
# of minions with errors: 0
-------------------------------------------
Expected behavior
Minions send responses only to the master that published the job.
Salt Version:
Salt: 3006.2Python Version:
Python: 3.10.12 (main, Aug 3 2023, 21:47:10) [GCC 11.2.0]Dependency Versions:
cffi: 1.14.6cherrypy: unknowndateutil: 2.8.1docker-py: Not Installedgitdb: Not Installedgitpython: Not InstalledJinja2: 3.1.2libgit2: Not Installedlooseversion: 1.0.2M2Crypto: Not InstalledMako: Not Installedmsgpack: 1.0.2msgpack-pure: Not Installedmysql-python: Not Installedpackaging: 22.0pycparser: 2.21pycrypto: Not Installedpycryptodome: 3.9.8pygit2: Not Installedpython-gnupg: 0.4.8PyYAML: 6.0.1PyZMQ: 23.2.0relenv: 0.13.3smmap: Not Installedtimelib: 0.2.4Tornado: 4.5.3ZMQ: 4.3.4System Versions:
dist: oracle 7.9 locale: utf-8machine: x86_64release: 4.1.12-124.60.1.el7uek.x86_64system: Linuxversion: Oracle Linux Server 7.9
Additional context
Saltstack Config also installed and integrated. It clearly shows multiple rows with responses which is confusing as the amount of rows is higher than number of targeted minions and one and the same information (return) is duplicated.
The text was updated successfully, but these errors were encountered:
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
Please be sure to review our Code of Conduct. Also, check out some of our community resources including:
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar.
If you have additional questions, email us at [email protected]. We’re glad you’ve joined our community and look forward to doing awesome things with you!
Description
When running jobs against v3006 minions, I can see job returns coming back to both masters.
When running the same job against v3004 minions, the job returns are coming back only to the master that initiated the job.
Setup
Multimaster setup, Active/Active, master version 3004.2
Steps to Reproduce the behavior
In this environment the minion named host01 is running version 3006.2 while the minion on master01 is running version 3004.2
Expected behavior
Minions send responses only to the master that published the job.
Screenshots
Versions Report
salt --versions-report
Additional context
Saltstack Config also installed and integrated. It clearly shows multiple rows with responses which is confusing as the amount of rows is higher than number of targeted minions and one and the same information (return) is duplicated.
The text was updated successfully, but these errors were encountered: