search

quarkslab / irma-ansible-old

IRMA ansible
24 stars 10 forks source link

Fix error when deploying IRMA using Vagrant > 1.7. #126

Closed guillaumededrie closed 8 years ago

guillaumededrie commented 8 years ago

With the new Vagrant "ansible.force_remote_user" option set to true by default, SSH User used to connect to the VM is now set to "vagrant" into the Ansible inventory (generated by Vagrant). This behavior does not permit to use Ansible "remote_user" option into playbooks (overridden by the inventory), that's the reason why the deployment fail.

guillaumededrie commented 8 years ago

Do Not Merge. @ch0k0bn, I think we should quickly merge this into master AND testing, as without this fix, It can't be possible for someone using Vagrant > 1.7 (default version on most of OS) to test IRMA.

If it's ok for you, please comment this PR and close it, I will manually merge it on the two branches.

FYI, the "official" response of the Vagrant Team: https://github.com/mitchellh/vagrant/issues/4854.

Regards.

ch0k0bn commented 8 years ago

agreed @guillaumededrie

guillaumededrie commented 8 years ago

Done.