I have an Ansible (2.13) machine targeting a remote centOS 6 with Python 3.6.
Remote machine has python3.6 installed and variables are set like this: $ ansible-inventory --host centos-6-vm { "ansible_private_key_file": "~/.ssh/id_rsa", "ansible_python_interpreter": "/usr/bin/python3.6", "ansible_user": "daniel" } Ansible can ping, setup and gather facts from target successfully. But when trying to run the yum module, I get an error as if my server doesn't have Python 3.6 This is my playbook --- - name: Deploy Services hosts: centos-6-vm gather_facts: true tasks: - name: Show python interpreter debug: var: "{{ item }}" with_items: - ansible_python_interpreter - ansible_python_version - name: Patch become: true yum: name: "*" security: true state: latest update_cache: true The first task is just to confirm that Ansible is recognizing Python versions. And the result is success. ok: [centos-6-vm] => (item=ansible_python_interpreter) => { "ansible_loop_var": "item", "ansible_python_interpreter": "/usr/bin/python3.6", "item": "ansible_python_interpreter" } ok: [centos-6-vm] => (item=ansible_python_version) => { "ansible_loop_var": "item", "ansible_python_version": "3.6.6", "item": "ansible_python_version" } But when it gets in the module, it gets an error saying no Python3. TASK [Patch] *********************************************************************************************************** fatal: [centos-6-vm]: FAILED! => {"changed": false, "msg": "ansible-core requires a minimum of Python2 version 2.7 or Python3 version 3.5. Current version: 2.6.6 (r266:84292, Aug 18 2016, 15:13:37) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)]"} Any idea how can I approach that? -- 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 ansible-project+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/3176afe0-d6fc-4e63-a4f8-94c20d3a7b16n%40googlegroups.com.