dispatch verbose output should include identify key file used
Reported by Alex-SF | December 16th, 2010 @ 09:35 AM | in Rundeck 1.0
The verbose output of dispatch shows node metadata like so:
$ tools/bin/dispatch --noqueue -p examples -I name='node1' -V --
uname -a Adding reference:
com.dtolabs.rundeck.core.cli.DefaultNodeDispatcher:node.name
Adding reference:
com.dtolabs.rundeck.core.cli.DefaultNodeDispatcher:node.user
executeNodeDispatch: number of nodes to dispatch to: 1,
(threadcount=1)
preparing for sequential execution...
Executing command on node: node1,
NodeEntryImpl{nodename=node1,hostname=192.168.1.102,type=Node,osName=null,osArch=null,osFamily=null,osVersion=null,username=user1,tags=[],attributes=null}
It should also include the SSH keyfile used (ie, framework.ssh.keyfile)
Comments and changes to this ticket
-
Deleted User December 16th, 2010 @ 03:24 PM
- State changed from “new” to “resolved”
(from [d2da1052aaec68a34b491f726f7d3014629718ba]) Add debug message to show ssh keyfile path on remote dispatch. [#132 state:resolved] https://github.com/dtolabs/rundeck/commit/d2da1052aaec68a34b491f726...
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.
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
People watching this ticket
Alex-SF
Referenced by
-
132
dispatch verbose output should include identify key file used
(from [d2da1052aaec68a34b491f726f7d3014629718ba])
Add deb...