ConfigurationFailure: SSH Password Not Set (When using ssh-password-option)

[Rob Byrne]

I've run into a bit of a bizarre issue. One of our nodes is using the standard SSH node executor, and is set up to use password authentication. I'm setting up the node to allow different jobs to run as different users. I've got the SSH username variable working (successfully executes a job as different users when using private key authentication).

However, when trying to use password authentication; and passing through a variable from the job with the Password (using ssh-password-option in the node definition, and then giving a path to a password in key storage); it seems to think no password is set. Here's the summary of the setup:

• Node with password authentication
  • password storage option of "${option.sshPassword1}"
  • In the job, I've created an option set to "Secure Remote Authentication". This points to the path of a user's SSH password. From my understanding, this should then work as the password for the SSH user.
  • When running the job, I receive the following error: "Failed: ConfigurationFailure: SSH Password was not set"

Any thoughts? I'm currently running Rundeck Community 4.8.

Thanks,

Rob

[rac...@rundeck.com]

Hi Rob,

Could you share the job definition and the model source node entry to take a look? (please edit any sensitive information).

Thanks!