Hi On Tue, Sep 23, 2014 at 06:27:30PM -0700, James Goodhouse wrote: > I am having some issues with a custom ssh_config file and not sure if I'm > doing > something wrong, if it's an ssh bug, or if it's an Ansible bug. > > I currently have a custom ssh_config file placed next to my ansible.cfg file. > In the ansible.cfg file I have the line ssh_args = -F ssh_config under the > [ssh_connection] section. Inside of my ssh_config file is the following: > > Host bastion > HostName xxx.xxx.xxx.xxx > User ubuntu > Host app01 > HostName xxx.xxx.xxx.xxx > ProxyCommand ssh bastion nc %h %p > User ubuntu > > If I then run the command ssh app01 -F ssh_config I receive the following > error: > > ssh: Could not resolve hostname bastion: nodename nor servname provided, or > not known > > However, if instead of referencing the ssh_config file, I instead place the > contents into ~/.ssh/config and run the command ssh app01, all is well and it > is able to resolve the hostname, bastion.
That makes sense. When you run "ssh app01 -F ssh_config", it will obviously use the given SSH config file.... But in order to connect to app01, it needs to run the ProxyCommand. But this will use the *default* ssh config file. Not the one in the current directory... As far as SSH is concerned, the ProxyCommand is simply a shell command - even if it just invokes ssh... -- Karl E. Jorgensen -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/20140924082019.GC14490%40hawking. For more options, visit https://groups.google.com/d/optout.
