-
Notifications
You must be signed in to change notification settings - Fork 100
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
ssh passphrase not working in rundeck ansible resource module #384
Comments
me too, this was working a week or so ago, going to try rolling back the plugin version plugin ver: 4.0.4 sorry, I should be more specific, I have some jobs where I actually pass the password via a rundeck job option, user enters password, now failing with
from cli though it woeks as expected
ansible.debug=true is showing me a null pointer exception
|
not sure if this is relevant but I am finding recently that (maybe this was always the case with Rundeck) when user input is involved with something on the Rundeck UI, Windows style CR/LF are finding there way into the system which is going to cause problems of course. An example is trying to use the key store to store an ssh key. If I use rd cli via bash to upload the key value from a file it works fine but if I copy/paste the key value data into the UI, no dice. I have a script that dumps my RD configs and some of the files when viewed with vim have the ^M line endings. I have a strong suspicion that my jobs that used to work via password entered into an "option" that are now failing is related to extra CR/LF's finding their way into places they should not be |
ssh passphrase not working in rundeck ansible resource module it is working in Node Executor using SSH
Getting Below error
It is working from cli
Rundeck version : 5.3.0
Ansible Version : 2.16.8
My Observations :
It seems that the issue may be related to the handling of the SSH key passphrase. Here are the key observations:
Summary
The root cause seems to be the handling and persistence of the SSH key passphrase. When the passphrase is entered and stored in the CLI session, the node becomes accessible. However, once the session expires or is reset, the passphrase needs to be re-entered for the node to be accessible again.
The text was updated successfully, but these errors were encountered: