Hi Team,
Ansible 2.8 will work on RHEL8 with python 3.6.
Reference : https://github.com/ansible/ansible/tree/stable-2.8
Thanks and Regards,
S Sathish
Hi Team,
Ansible 2.8 will work on RHEL8 with python 3.6.
Reference : https://github.com/ansible/ansible/tree/stable-2.8
Thanks and Regards,
S Sathish
Why would you want to? Why would you not use the available
ansible-core 2.12 RPM?
Let's keep "ansible" and "ansible-core" straight, by the way. Ansible
got re factored some years back, and what's in the github repo called
"ansible" is packaged as "ansible-core" over at pypi.org, even though
it's python modules are all referred to as "ansible" modules, and the
tarball should really be called "ansible". The package now called
"ansible" contains not a single line of those modules or the
executable tools. It's a collection of more than 100 third-party
ansible galaxy collection modules, assembled by tools at
https://github.com/ansible-community/ansible-build-dat, and the python
module directory in which they are installed is called
"ansible_collections" just as the tarball should be called
"ansible_collections" over at pypi.org.
This comes up often enough that it's a sensitive subject, and the
developers are probably pretty tired of hearing that the labels are so
consistently confusing.
Hi Team,
Currently we are using ansible 2.8 on top of RHEL 7 with consist of python2.7
we need to understand ansible 2.8 will work on python3.6 system(RHEL 8) or it will work only on python2.7 system(RHEL7).
Thanks and Regards,
S Sathish
Hello Satish,
this was reported on ansible 2.7 documentation:
Currently Ansible can be run from any machine with Python 2 (version 2.7) or Python 3 (versions 3.5 and higher) installed.
Anyway i suggest you to switch to ansible 2.9 which is the latest supported version of ansible 2.x branch. Migrating from 2.8 is not hard.
Luca
Luca
Thanks Luca for below clarity.
While checking ansible 2.9 already “Unmaintained (end of life)” , how we are saying ansible 2.9 is latest supported version of ansible 2.x branch.
https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html
Thanks and Regards,
S Sathish
Hello,
i was not up to date with community deprecation of 2.9. I’m using ansible 2.9 from redhat 7.
Luca
ansbile-core 2.13 is the latest version as of this post.
Hi Brian/Team,
In RHEL 8.6 come with python3.6 as default with Long term support. As application system we need to stick with long term support package.
As per ansible-core 2.13 requirement sheet dependencies Python 3.8+ support required is mentioned.
our question ansible-core 2.13 will able to compile, build ansible-core rpm and execute ansible functionality using python3.6 will work?
https://github.com/ansible/ansible/blob/stable-2.13/requirements.txt
Python3 support document below link it say ansible2.5 onward support python3 with version of Python 3.5 or greater.
https://docs.ansible.com/ansible/latest/reference_appendices/python_3_support.html
Thanks and Regards,
S Sathish
Hi Brian/Team,
In RHEL 8.6 come with python3.6 as default with Long term support. As application system we need to stick with long term support package.
As per ansible-core 2.13 requirement sheet dependencies Python 3.8+ support required is mentioned.
our question ansible-core 2.13 will able to compile, build ansible-core rpm and execute ansible functionality using python3.6 will work?
https://github.com/ansible/ansible/blob/stable-2.13/requirements.txt
It can be easily built with "pip3.8 install --user ansible-core"
Compiling it as an RPM is.... notably harder, because it relies on
jinja2 >= 3.0.0, and building up the dependency chain as RPMs is...
well, it's painful. I publish RPM building tools over at
https://github.com/nkadel/ansiblerepo/, and you're welcome to play
with them. The full suite of dependencies being built up for Fedora
is.... much, much larger, because someone elected to add "pywinrm",
which has a very large dependency chain.
Python3 support document below link it say ansible2.5 onward support python3 with version of Python 3.5 or greater.
https://docs.ansible.com/ansible/latest/reference_appendices/python_3_support.html
Those directions do not install the most current release of
ansible-core, because they use the default python3 and install
somewhat older versions. It's confusing.
Also note that the 'ansible core' and the 'ansible targets' have
different dependencies, core in general requires newer python and
keeps compatibility for modules to execute on older pythons on the
target.
Also note that the 'ansible core' and the 'ansible targets' have
different dependencies, core in general requires newer python and
keeps compatibility for modules to execute on older pythons on the
target.
Frankly, the current "ansible" package should never be instlalled
anywhere by default. It's not needed, at all. ansible-core contains
all the important python modules and executable tools, except for a
very bulky and unnecessary suite of roughly 100 third party modules,
only a few of which are of use on a normal ansible sysetup and each of
which can be installed more efficientlywith the ansible galaxy
collection commands.
Stick to ansiblc-core.. There are RPMs for ansibl-core 2.12 on RHEL 8
and RHEL 9, and ansible-core 2.13 can be installed with the python38
optional installation if you feel the need. I publish RPM building
tools for ansible 6 and ansible-core 2.13 over at
https://github.com/nkadel/ansiblerepo/, if you feel the need to that
upgrade in the short term, but I don't recommend it for production use
yet. ansible-core 2.13.1 upstream relies on "pywinrm", and the
dependency chain for that is a nightmare.
Nico Kadel-Garcia