#515 ✓resolved
Matt Wise

Nodes require a 'username' field, when they are supposed to fall back to project.ssh.user setting

Reported by Matt Wise | February 8th, 2012 @ 11:16 AM | in Rundeck 1.4.2 (closed)

Right now if you use an external nodes file, that file is required to pass a 'username=' field for each host. Without this, the doc states that RunDeck will fall back to a project-setting and then a rundeck-setting for the username. This does not work right now, and throws this error:

Failed dispatching to node bastion-20417898.xxx.com: com.dtolabs.rundeck.core.execution.ExecutionException: Username must be set to connect to remote node 'bastion-20417898.xxx.com'
07:08:06 Execution failed on the following 1 nodes: {bastion-20417898.cloud.nextdoor.com=[Workflow : exception: com.dtolabs.rundeck.core.execution.workflow.WorkflowStepFailureException: Step 1 of the workflow threw exception: Execution failed on the following 1 nodes: {bastion-20417898.xxx.com=Error dispatching command to the node: com.dtolabs.rundeck.core.execution.ExecutionException: Username must be set to connect to remote node 'bastion-20417898.xxx.com'}]}

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues

Shared Ticket Bins

People watching this ticket

Tags

Pages