-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] salt-ssh render pillar twice (once as master, once as minion) #62230
Comments
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.
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. |
We're also affected by this issue. Additionally, Versions Report salt --versions-report# salt --versions-report
Salt Version:
Salt: 3004.1
Dependency Versions:
cffi: 1.15.0
cherrypy: unknown
dateutil: 2.8.1
docker-py: 4.1.0
gitdb: 4.0.5
gitpython: 3.1.24
Jinja2: 2.11.3
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.0
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.9.7
pygit2: Not Installed
Python: 3.9.2 (default, Feb 28 2021, 17:03:44)
python-gnupg: Not Installed
PyYAML: 5.3.1
PyZMQ: 20.0.0
smmap: 4.0.0
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: debian 11 bullseye
locale: utf-8
machine: x86_64
release: 5.10.0-13-amd64
system: Linux
version: Debian GNU/Linux 11 bullseye salt-ssh --versions-report# salt-ssh --versions-report
Salt Version:
Salt: 3004.1
Dependency Versions:
cffi: 1.15.0
cherrypy: 18.6.1
dateutil: 2.8.1
docker-py: 4.1.0
gitdb: 4.0.5
gitpython: 3.1.24
Jinja2: 2.11.3
libgit2: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack: 1.0.0
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.21
pycrypto: Not Installed
pycryptodome: 3.9.7
pygit2: Not Installed
Python: 3.9.2 (default, Feb 28 2021, 17:03:44)
python-gnupg: Not Installed
PyYAML: 5.3.1
PyZMQ: 20.0.0
smmap: 4.0.0
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: debian 11 bullseye
locale: utf-8
machine: x86_64
release: 5.10.0-13-amd64
system: Linux
version: Debian GNU/Linux 11 bullseye |
Closing as fixed per #65067 (comment) |
Description
Pillar rendering (tested with python she-bang and ext_pillar) happens twice when using salt-ssh: once in the master context, once in the minion context.
Setup
Using Debian bullseye vms (official cloud image) running on a private openstack cloud. Using official salt latest repo. Nothing beside salt installed. Everything up-to-date.
Steps to Reproduce the behavior
I setup a configuration key on the master and then read it in a python pillar (this is obviously totally useless but the simplest way I found to reproduce/show the problem).
When applying or displaying the state using master + minion, everything works as expected:
But when using salt-ssh:
The pillar appear to be rendered twice (see warning at the start) and the second time does not have access to the master's configuration. The first render appears to work as intended as the value is present in the pillar.
Expected behavior
State should behave the same when using salt-ssh and render the pillar only once, on the master.
Versions Report
salt --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)salt-ssh --versions-report
(Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)The text was updated successfully, but these errors were encountered: