I did some experimenting with this about a year ago.  I have a repo that
has a playbook that can build the packages for EL5 using python2.6 from
EPEL.

NOTE: I don't necessarily recommend this, it was an experiment to see if it
could be done

WARNING: Proceed at your own risk ;)

https://github.com/sivel/el5-python26-rpm

The last release of Ansible to support EL5 natively was Ansible 2.3

On Fri, Mar 8, 2019 at 4:16 PM S C Rigler <[email protected]> wrote:

> If you can install a newer python on the machines you should be able
> to manage them by setting the inventory variable
> "ansible_python_interpreter" for them to the path of the alternate
> python interpreter.
>
> On Fri, Mar 8, 2019 at 2:25 PM Adam E <[email protected]> wrote:
> >
> > hey there, i'm trying to manage a bunch of centos5/rhel5 systems with
> ansible 2.7.5
> >
> > On the target host I am able to install python 2.6 from epel which is
> all good and ansible runs just fine for most stuff.   The issue is with
> anything related to packages (ie . package_facts and package).  They both
> rely on the "rpm" python library.
> >
> >
> > Problem is, I can't figure out how to install this library on centos 5.
>  It seems the library is not available in epel
> >
> > I tried building from source but I then get the error below:
> > # python26
> > Python 2.6.8 (unknown, Nov  7 2012, 14:47:45)
> > [GCC 4.1.2 20080704 (Red Hat 4.1.2-52)] on linux2
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import rpm
> > rpm.py:15: UserWarning: The RPM Python bindings are not currently
> available via PyPI.
> >
> >
> > Please install them with your distro package manager (typically called
> > 'python2-rpm' or 'python3-rpm'), and ensure that any virtual environments
> > needing the API are configured to be able to see the system site packages
> > directory.
> >
> >
> >   warnings.warn(warning_msg)
> > >>>
> >
> >
> > If I can't get this working, I guess my only options are to either just
> not manage packages on the legacy centos/rhel5 boxes or see about running
> an older version (multiple versions) of ansible within AWX.
> >
> > Just wondering if anyone has went through this already and can provide
> any tips.
> >
> > --
> > 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/18a045ee-1f63-437b-a8c5-d10880e5cd50%40googlegroups.com
> .
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> 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/CAFbiokdgxMddo%3D-DP%2B5LVrGqyL_4PoHAddii%2BWH2cscEKhtbyA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Matt Martz
@sivel
sivel.net

-- 
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/CAD8N0v84Nf1P5KCPePKv_wgLte4W3q1XhAsJ2SGeSnC%3DEyPZYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to