Le mardi 08 novembre 2016 à 11:23 +0530, Kushal Das a écrit :

On 08/11/16, Danishka Navin wrote:

...

Hi team,

Is there any specific reason to drop python from Fedora AMIs in AWS?

Standard Fedora Cloud images are Python3 only as we moved to Python3 as default. Only the Atomic images have Python2 as we can not install new packages on it (and Python2 is required for ansible).

With the release of Ansible 2.2, Python 3 should be usable. As I keep saying everywhere, I was able to deploy openshift (using openshift-ansible) on Fedora 24 with python 3 (minus a few fix but 2.2 should be working enough to not break right away).

That's not considered yet prime time ready by upstream, because we didn't do enough testing, but people should be able to try and report bugs on 2.2, albeit I would recommend testing on git devel branch before filling a bug.

To summarize: - the syntax of all modules is tested to be python 3 ready - all but 3 regression tests are running on python 3 (2 being for infra reasons, 1 because the bug produce a error string bigger than my 14" screen with string comparaison) - we did deploy non trivial infra with it, and the most common modules used on a remote system should be fine - upstream want more backtrace (at least, I want)

If people see errors on 2.2 (or devel), they can ask on #ansible-devel, we will be happy to help and produce a fix.