Hi Ian,
Excellent News!
Best regards,
Gilles
Le mercredi 12 octobre 2016 10:13:16 UTC+2, Ian Smith a écrit :
>
> Hi Gilles,
>
> Sorry error between chair and keyboard this time. Now that the override
> file is being read there was an ansible_ssh_host line in the override file
> which overrode
Hi Gilles,
Sorry error between chair and keyboard this time. Now that the override
file is being read there was an ansible_ssh_host line in the override file
which overrode the Vagrant generated one in the inventory. Removing that
line now means that the deployment now completes.
Many thanks
Hi Gilles,
Thank you for that tip. I can see that the override file is now being used
as expected. However the problem is now that the override server name is
correctly being used the initial vagrant ssh connection to create the user
is attempting to connect to the IP address of the server not
Hey Ian!
Thank you for bringing more details, which helped me to figure out where is
the "second" problem (very probably).
I think that the two variants below should fix your problem:
1) [recommended] use the extra_vars option
Having spent time on and off today looking at this and comparing the output
of the ansible log as well as the console I think the ssh method described
is correct. The issue appears to be that the key required is not being
installed. The ansible script in question uses override JSON file to
Hi Gilles,
I *think* I see where you are going with this but it ends up with the
following error message " UNREACHABLE! => {"changed": false, "msg": "Failed
to connect to the host via ssh.", "unreachable": true}"
Running ansible directly the following commands work
ansible-playbook -v -e
Hi Ian,
As of Vagrant 1.8+ the Ansible remote user is forced by default. Therefore
your use case requires to set the "force_remote_user" option to *false*.
See:
-
https://www.vagrantup.com/docs/provisioning/ansible.html#force_remote_user
-
