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
Salt-ssh cannot do simple state 'test.nop': "'test.nop' is not available." #27636
Comments
Have you tried removing the local cache ( |
I think this is actually "expected behavior", though it is confusing because of the If you check the I was wondering when we would run into something like this in the docs with our merge-forward strategy. I'm not sure what the best way is to inidcate these discrepancies in the docs or not. Thoughts @jacobhammons or @basepi? |
Yes, I thought about this very problem when I wrote that versionadded. I probably should have just put 2015.8.1, and if people discovered it in 2015.5.6 it would just be a happy surprise for them. I think that's what we should do in the future -- only include the latest stable version. |
(If someone wants to change it to 2015.8.1, I would be on board. I'll do it tomorrow if nobody else grabs it) |
Removing the /tmp/.<salt_user>_*_salt cache worked, at least for my archive.extracted state. Still not for the test.nop, but sounds like that is expected for the version. Thanks for the help. The archive.extracted was much more important anyway. |
Hello, I was trying to use the
archive.extracted
state using salt-ssh, when I recieved errors that the statearchive.extracted
is not available. It turns out I cannot get any state that is not afile.*
state. Is this normal behavior?Here is my state bar.sls:
Which after running
salt-ssh 'hostname.com' --config-dir=<conf-dir> --priv=<ssh-id> state.sls bar
has output:salt-ssh versions output:
The text was updated successfully, but these errors were encountered: