Provisioning Ubuntu 16.04 Vagrant with Ansible fails on chown

SOLOUTION#1\n\nUbuntu 16.04 has python3, not 2.7.x. and Ansible doesn't support for Python 3 yet.\n\nFor Ubuntu 16.04 I use the following play to get Python 2.7 installed. \n\n---\n- hosts: xenials \n gather_facts: no\n become: yes\n tasks:\n - name: Install python 2.7 \n raw: apt-get update -qq && apt-get install -qq python2.7\n\n - name: check if softlink exists\n stat:\n path: /usr/bin/python\n register: python_file\n\n - name: create softlink for python 2.7\n raw: ln -s /usr/bin/python2.7 /usr/bin/python\n when: python_file.stat.islnk is not defined\n\n - name: Ensure /srv/web exists\n file:\n path: /srv/web\n state: directory\n mode: 0755\n owner: \"{{ remote_user }}\" # hope you have defined this variable in your ansible.cfg\n\n\nkey line is gather_facts: no which prevents Ansible to execute code on the remote server that the remote server cannot yet support.Without this line,play would fail. \n\nThat provides an /usr/bin/python2.7, which I explicitly point to in my inventory file. \n\n[xenials] \n192.168.33.100 \n\n[xenials:vars] \nansible_python_interpreter=/usr/bin/python2.7 \n\n\nNote that there is nothing special about the name xenials. It's just a group I have defined in my inventory. \n\nThis ansible_python_interpreter only need for the first time, after that you can remove it because we have created the softlink for the python2.7\nHope that help you.\n\nSOLOUTION#2\n\nReason of this error:\n\nI have reviewed the gist that contain the detail log and figured out this:\n\n\nI am sure you are using the official vagrant box ubuntu/xenial64\nThis official vagrant box doesn't have vagrant user\n\n\"msg\": \"chown failed: failed to look up user vagrant\" that's the error trace which help you find the exact error.\n\n\nSolution-1 to this error:\n\nDownload some other vagrant box, I recommend this vagrant box geerlingguy/ubuntu1604 it has really good reputation\n\nSolution-2 to this error:\n\nWith the official vagrant box, you can do the same as I am doing to mitigate this error. Add the following to your Vagrantfile:\n\nconfig.vm.provision \"shell\" do |s|\n ssh_pub_key = File.readlines(\"#{Dir.home}/.ssh/id_rsa.pub\").first.strip\n ssh_user = ENV['USER']\n s.inline = <<-SHELL\n adduser --disabled-password --gecos \"\" #{ssh_user}\n mkdir -p /home/#{ssh_user}/.ssh\n touch /home/#{ssh_user}/.ssh/authorized_keys\n chown -R #{ssh_user}. /home/#{ssh_user}/.ssh\n echo \"#{ssh_user} ALL=(ALL) NOPASSWD:ALL\" > /etc/sudoers.d/99-#{ssh_user}\n echo #{ssh_pub_key} >> /home/#{ssh_user}/.ssh/authorized_keys\n chmod 0440 /etc/sudoers.d/99-#{ssh_user}\n SHELL\n end\n\n\nWhat it will do is, just create your host login user to the guest and upload the rsa key for it. So you can run the playbook to the vagrant machine as if it is the remote machine. If you'll face any problem further, please let me know.\n\nHope this help you.",