Update Ansible to 2.6+ due to Python 3.7

[Marcin Juszkiewicz]

We use Ansible 2.4.0 as minimum. Kolla-toolbox image uses 2.2.0 even...

Debian has Python 3.7 which makes both those version borken due to 'async' variable used in Ansible source code as it is now Python keyword.

Minimal version would be 2.5.x but it is not supported by upstream anymore. Therefore 2.6 or 2.7 should be used.

Debian stretch has 2.7.5 in backports, Debian buster has 2.7.7 version. CentOS has 2.8 available, Fedora is on 2.8 as well. Ubuntu 18.04 is on 2.5.1 which is known to be broken so users of that distribution will have to install newer one.

[Marcin Juszkiewicz (hrw)]

17:34 < mgoddard> hrw: is that the earliest version that supports py3.7?

17:43 < hrw> 17:42 < hrw> which version of ansible is the first one working with Python 3.7?
17:43 < hrw> 17:42 <@sivel> hrw: Ansible 2.5 iirc, due to the reserved async keyword
17:43 < hrw> 17:43 <@sivel> 2.5 is no unsupported anyway, so 2.6+ should all work and support Python 3.7
17:43 < hrw> mgoddard: so 2.6.0 should be new minimal
17:46 < mgoddard> hrw: seems reasonable, it's been out for a while now. Should we say it is minimum for py3 or py2 as well?
17:49 < hrw> mgoddard: 2.6.0 minimum.
17:49 < hrw> no py3 or py2. no ubuntu or centos or debian
17:49 < hrw> just ansible_version_min: 2.6.0
17:50 < mgoddard> do all supported distros provide that as a minimum?
17:51 < kplant> centos7 is still shipping 2.4 in the repo
17:51 < hrw> Debian has 2.7.5 (stretch-backports) 2.7.7 (buster), CentOS has even 2.8 in ovirt repos
17:51 < kplant> though epel-release and others have 2.8
17:51 < kplant> ^ what he said
17:51 < hrw> ubuntu 18.04 has 2.5.1
17:52 < mgoddard> hmm
17:52 < hrw> which is already unsupported by upstream
17:52 < hrw> so they can always 'pip install ansible==2.6.0' or sth
17:52 < mgoddard> but presumably supported downstream?
17:53 < hrw> mgoddard: ansible is in universe part not main
17:53 < mgoddard> ok
17:54 < hrw> https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1780278 is an old bug saying 2.5.1 is unusable. completelly ignored
17:54 <@openstack> Launchpad bug 1780278 in ansible (Ubuntu) "ansible 2.5.1 need upgrade to 2.5.2 or 2.5.3 (bug with set_facts)" [Undecided,Confirmed]
17:55 < mgoddard> hrw: https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html#install-dependencies-not-using-a-virtual-environment
17:55 < hrw> rest of their bugs can be summaried: 2.5.1 is broken
17:55 < mgoddard> ok
17:56 < mgoddard> let's go for 2.6 then
17:56 < hrw> mgoddard: in other words: docs needs update too
17:56 < hrw> mnasiadka: ping
17:57 < mnasiadka> 2.6 is a safe go I guess
17:57 < mnasiadka> but about kolla-toolbox - maybe it's better to go 2.8 in the image, so we don't have to move when 2.6 gets dropped
17:58 < hrw> mnasiadka: so 2.6 as minimum, kolla-toolbox to 2.8 and then update playbooks/etc according to 2.8 porting guide?
17:58 < hrw> mnasiadka: or according to 2.6 porting guide to be safe?
18:01 < mnasiadka> hrw: ansible support lasts for 3 releases, so when 2.9 goes out (in 4-5 months) - 2.6 is dead
18:01 < mnasiadka> mgoddard: ideas?
18:01 < hrw> 2.7.0?
18:02 < mnasiadka> probably that's the safe approach
18:02 < mnasiadka> maybe let's add it as a topic for tomorrow's meeting
18:02 < mgoddard> 2.7 is probably a good compromise
18:03 < mgoddard> although we're only at the start of the release so 2.8 might be more stable by the end
18:04 < hrw> mgoddard: 2.7 is in Debian now.
18:04 < hrw> 2.8 is not yet there
18:05 < mgoddard> hrw: I meant for kolla-toolbox, where we install via pip