Hi, The latest devel is V2 version of ansible, and it seems like a bug, would you mind raising a bug in github.
- Benno On Wed, Jun 10, 2015 at 9:34 AM, Michael Legleux <[email protected]> wrote: > I don't know how much more basic to make this. > I have an ansible-test directory structured like this: > > ansible.cfg that contains: > [defaults] > inventory = ./hosts.yml > > *host_vars/ubu.yml* > --- > ansible_ssh_host: 192.168.1.32 > ansible_ssh_user: vagrant > ansible_ssh_pass: vagrant > > *hosts.yml* > [all:children] > ubuntu > windows > > [ubuntu] > ubu > > [windows] > win8 > > An ansible 1.9.2 checkout from minutes ago running this command returns: > ansible ubu -m ping > ubu | success >> { > "changed": false, > "ping": "pong" > } > checkout devel and I get this: > ansible ubu -m ping -vvvvv > <ubu> ESTABLISH SSH CONNECTION FOR USER: emel > <ubu> EXEC ssh -C -tt -vvv -o ControlMaster=auto -o ControlPersist=60s -o > ControlPath="/tmp/ansible-ssh-%h-%p-%r" -o KbdInteractiveAuthentication=no > -o > PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey > -o PasswordAuthentication=no -o ConnectTimeout=15 ubu mkdir -p > $HOME/.ansible/tmp/ansible-tmp-1433908585.06-206437845695787 && chmod a+rx > $HOME/.ansible/tmp/ansible-tmp-1433908585.06-206437845695787 && echo > $HOME/.ansible/tmp/ansible-tmp-1433908585.06-206437845695787 > ubu | FAILED! => {'msg': u'ERROR! SSH encountered an unknown error. The > output was:\nOpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014\r\ndebug1: Reading > configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line > 19: Applying options for *\r\ndebug1: auto-mux: Trying existing > master\r\ndebug1: Control socket "/tmp/ansible-ssh-ubu-22-emel" does not > exist\r\nssh: Could not resolve hostname ubu: Name or service not > known\r\n', 'failed': True} > > As the error says, it's trying to connect with user emel. Which is my > first question, what happened to the host_vars? > providing "-u vagrant" (which is the only account on the vm) fails with > the exact same error, so it's not just the vars not getting read that's the > problem. > > > > > > -- > 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/936b4b50-06e8-4f26-8c3b-e6a0998dce82%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/936b4b50-06e8-4f26-8c3b-e6a0998dce82%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAFUV_d6kbe1BL%3D005O3M%2BZA0kYFs1FDo6%2BBzMAqjjVfWsv0MtA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
