-
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 no longer applies roster defaults to hosts not explicitly listed in the roster #59369
Comments
I'm not able to replicate this. Which Salt-SSH roster are you using? |
I'm using the default static yaml roster. hosts in the roster correctly get the defaults, but hosts not in the roster don't. so for instance, if I have a new host on my network and run it's easy to demonstrate by putting an entry for the host with its hostname in the roster, and then comparing the run with the hostname vs the IP. the hostname, which is in the roster, executes correctly. but the IP always dies with:
I'm currently running on Arch, with salt 3004. |
Thanks for clarifying. I am able to replicate this now. Do you happen to know in which version it was working? |
I don't remember, sorry. as you can see, I filed this in Jan of last year, and it was broken for a little while before that, so hopefully that'll help you bisect it. |
Well I got the same, I guess the last time roster_defaults may was working must have been around salt 3000 to 3001 but unsure. |
Duplicate of #58440 |
Description
used to be able to just run
salt-ssh
against any host using the configured roster defaults by hostname. at some point in the recent past, this has broken, so now all hosts have to be manually defined in the roster file.Setup
Steps to Reproduce the behavior
salt-ssh
against a host not explicitly defined in the roster fileroster_defaults:
priv: agent-forwarding
sudo: True
tty: True
user: tessa
Expected behavior
I expected it to use my username and sudo to run the states against the remote host. not just try root and fail.
Versions Report
salt --versions-report
```yaml Salt Version: Salt: 3002.2Dependency Versions:
cffi: 1.14.3
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: 4.3.1
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 2.11.2
libgit2: Not Installed
M2Crypto: Not Installed
Mako: 1.1.4
msgpack: 0.6.2
msgpack-pure: Not Installed
mysql-python: Not Installed
pycparser: 2.20
pycrypto: 2.6.1
pycryptodome: 3.9.8
pygit2: Not Installed
Python: 3.8.6 (default, Sep 25 2020, 09:36:53)
python-gnupg: Not Installed
PyYAML: 5.3.1
PyZMQ: 19.0.1
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.2
System Versions:
dist: ubuntu 20.10 groovy
locale: utf-8
machine: x86_64
release: 5.8.0-40-lowlatency
system: Linux
version: Ubuntu 20.10 groovy
The text was updated successfully, but these errors were encountered: