Closed Jinkxed closed 7 years ago
Nevermind I found the issue. This really should be noted in the documentation somewhere.
If you want to use the privateIPaddress of your ec2 instances, add this to your mapping file or just copy and paste the default and change:
hostname.selector=privateIpAddress
Thank you! This definitely should be highlighted in documentation.
I am going to re-open this and rename. I think the default mapping should also include the privateIpAddress as a fallback.
I have hostname.selector=privateDnsName in mapping params, but when I search for nodes under command section, I get 2 hostnames - one is null and other other one is the private dns. Since one is coming as null, I am unable to execute the query . Please help.
15:02:01 i-01addfae Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-01addfae' 15:02:01 i-0e638cdf Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-0e638cdf' 15:02:01 i-2335778c Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-2335778c' 15:02:01 i-27ce8e88 Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-27ce8e88' 15:02:01 i-2b8dc084 Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-2b8dc084' 15:02:01 i-7a3765d5 Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-7a3765d5' 15:02:01 i-813c7e2e Failed: ConfigurationFailure: Hostname must be set to connect to remote node 'i-813c7e2e'
Hey,
So I'm getting all this working and noticed that anything that requires SSH to a remote node, the rundeck server seems to using its own local ip instead. I think maybe it's not mapping the privateipaddress correctly for the remote node?
Example: