Andreas, when I implemented this, I had to put a line in the section to use sudo for the installation, which makes sense, just wondering if you had achieved that another way , just curious.
I initially did these manually for testing, but this is obviously a much better solution for large scale roll outs, without having to update the AMI first. Thanks for the post. Cheers Nick On Sunday, 24 April 2016 20:38:14 UTC+1, Andreas Olsson wrote: > > On sön, 2016-04-24 at 12:00 -0700, Peter Loron wrote: > > I'm trying to provision a Ubuntu 16.04 server machine. When running > > a playbook which has worked fine on Ubuntu 14.x and 15.x, it fails > > with this error: > > ... > > Ubuntu 16.04 has python3, not 2.7.x. Why is this not being > > autodetected? > > No Ansible support for Python 3 just yet. > > > https://docs.ansible.com/ansible/faq.html#how-do-i-handle-python-pathing-not-having-a-python-2-x-in-usr-bin-python-on-a-remote-machine > > > For Ubuntu 16.04 I use the following play to get Python 2.7 installed. > > - hosts: xenials > gather_facts: False > tasks: > - name: apt-get update > raw: apt-get update -qq > - name: Install python 2.7 > raw: apt-get install -qq python2.7 > > That provides an /usr/bin/python2.7, which I explicitly point to in my > inventory file. > > [xenials:vars] > ansible_python_interpreter=/usr/bin/python2.7 > > Do note that there is nothing special about the name xenials. It's just > a group I have defined in my inventory. > > // Andreas > -- 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/b0e576a9-1580-40ca-b3f3-6eccc78d56c3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
