sshj plugin ignoring option.username

236 views
Skip to first unread message

Russ Robinson

unread,
Jul 28, 2021, 10:08:00 AM7/28/21
to rundeck-discuss
In one of my Rundeck 3.4.1 environments; I have a job which is not able to ssh into target nodes but receives "Failed: Unknown: Exhausted available authentication methods".  If I look at the job in debug mode, I see:

[sshj-ssh] username: rundeck

However, my job has an option called "username".  Within my project settings, it contains:

project.ssh.user=${option.username}

I also have in the node's definition:

"username": "${option.username}",

So I'm baffled as to why Rundeck is sending in username of "rundeck".  Oddly, some of my other Rundeck environments (same 3.4.1 release, same project settings, and same node settings) are working fine.  Am I overlooking a cache or something?

rac...@rundeck.com

unread,
Jul 28, 2021, 1:39:15 PM7/28/21
to rundeck-discuss
Hi Russ,

Could you double-check your model source file? Maybe an blank space is the cause of that issue.

Regards.

Russ Robinson

unread,
Jul 28, 2021, 2:42:27 PM7/28/21
to rundeck-discuss
I checked:

grep -i username nodes_final.json | sort -u
    "username": "${option.username}",

Russ Robinson

unread,
Jul 28, 2021, 7:07:37 PM7/28/21
to rundeck...@googlegroups.com
Problem found … bad/corrupt node inventory file.

Thanks,
Russ

On Jul 28, 2021, at 2:42 PM, Russ Robinson <eagl...@gmail.com> wrote:


--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/f692b30f-015f-4ed0-bddc-014806dcd707n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages