Bdtyktl

How can Ansible be used via Vagrant's ansible provider while working with actions that become a superuser? Every attempt I've made so far doesn't work for quite inexplicable reasons.

The scenario is annotating an apt action with become to give it the right permissions. The Ansible invocation, which is triggered with vagrant provision, is SSHing in via the vagrant user (which Vagrant now enforces by default via the ansible provider), a user that has passwordless sudo by default on two base boxes I've tried: ubuntu/trusty64 and debian/stretch64.

Despite passwordless sudo apparently being supported on the underlying VM, this doesn't work and yields the following error:

fatal: [default]: FAILED! => {"changed": false, "module_stderr": "sudo: a password is requiredn", "module_stdout": "", "msg": "MODULE FAILUREnSee stdout/stderr for the exact error", "rc": 1}  

As Vagrant boxes use the vagrant/vagrant for username and passwords on boxes by default, I then update the Vagrantfile to ask for a sudo password explicitly:

config.vm.provision "ansible" do |ansible|

  ansible.playbook = 'main.yml'

  ansible.ask_become_pass = true

Which prompts for a password:

   default: Running ansible-playbook...

SUDO password:

However, after entering vagrant it still fails, even though I can use vagrant ssh to enter the VM and confirm this is the correct password:

fatal: [default]: FAILED! => {"changed": false, "module_stderr": "Sorry, try again.n[sudo via ansible, key=XXXXXXXXXXXXXXXXXXX] password: nsudo: 1 incorrect password attemptn", "module_stdout": "", "msg": "MODULE FAILUREnSee stdout/stderr for the exact error", "rc": 1}

Interestingly, the ansible_local provider works fine for the ubuntu/trusty64 box but fails with debian/stretch64 for completely unrelated reasons. So it seems to be specifically to do with the interplay between Vagrant and Ansible over SSH with sudo.

Information on my Vagrant and Ansible installations:

$ ansible --version

ansible 2.7.1

  config file = None

  configured module search path = ['/Users/XXXXXX/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']                                                                                   

  ansible python module location = /usr/local/lib/python3.7/site-packages/ansible

  executable location = /usr/local/bin/ansible

  python version = 3.7.1 (default, Nov  6 2018, 18:46:03) [Clang 10.0.0 (clang-1000.11.45.5)]

$ vagrant --version

Vagrant 2.2.2

What is the current recommended reliable way of using Vagrant's ansible provisioner with become? Thanks.