Closed dmasteller4 closed 1 year ago
This change has caused a lot of issues with Ansible on our systems. We can no longer run Ansible from a Centos Stream 8 host unless we are installing Ansible in a venv created from the system Python (3.6). It would generally be fine for this to fail and not load the selinux bindings in our case because this is our Ansible controller but since this package is hard-coded to look only at /usr/bin/python...
🤷♂️
The 0.3.0
release has major breaking changes in it but it is a minor release made during a holiday, on a weekend. Seems like a questionable choice.
Similar to 'change to platform-python #48 #49', we were having an issue with python3-selinux binding looking in the wrong site packages directory when multiple versions of python are installed. This fix grabs more fields of
platform.python_version_tuple()
, ensuring it is getting the site packages from the python version that is actually running.Ansible error encountered:
Note the
discovered_interpreter_python
is python3.8, but the selinux python bindings detection is being done under python3.7/usr/local/lib/python3.7/site-packages
Using the commit from this PR fixed the problem for us.
Fixes: #48 Fixes: #49