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 using machine IP to execute commands, without having to write a roster file #26689
Comments
@double-yaya I was able to confirm that this is working on salt version 2014.1.4 and not working on salt version 2015.5.3. Thanks for your report. |
Similar to issue saltstack#26689, but I am using the cloud roster file to get the IP targets generated from running salt-cloud.
Similar to issue saltstack#26689, but I am using the cloud roster file to get the IP targets generated from running salt-cloud.
Hi, i have the same issue, and found the answer. salt-ssh --roster=scan 'IP' test.ping --user=SSH_USER --passwd=SSH_PASSWD |
What is your version @yangxiangyu |
salt-ssh 2015.5.2 (Lithium) |
I am surprised this ever worked. The scan roster was always the intended solution here. The scan roster can also be used against a subnet if you want to go crazy. With the answer posted I am going to close this issue out |
I run this command in salt-ssh 2015.8.8, return True:
the result is this:
However, I run this by python api,return error:
the error is this:
|
The default vagrant user is |
Why cmdline is OK, the python api is wrong?What's the difference between them?the root's password is 'vagrant', user+password matching is not enough? |
Still wrong when I use vagrant/vagrant |
Oh, I follow you now, sorry I read it too quickly the first time. This should work, I am not sure off the top of my head what is missing, but this should be a new issue, can you please open a new issue to track this please? |
Ok |
In 2014.1.4 version I can specify the target machine execute commands, the target machine not written in the roster file
command like this:
But in 2015.5.3 version failed
result:
So.....In 2015.5.3 version,the target machine must be written in a roster file?
The text was updated successfully, but these errors were encountered: