-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-navigator 24.3.2 attempts to load python 3.9 library instead of 3.12 when inspecting EE images #1766
Comments
Please remove the cache first and also provide more information about which python interpreter is used to execute navigator. |
This is a good find. Can you confirm the python version inside the EE? The |
I cleared the ansible-navigatgor cache using "# rm ~/.cache/ansible-navigator/*" and tried again. I received the same result. On Fedora 40 I am using the default python 3.12. I have several EE's I can inspect: quay.io/ansible/awx-ee:latest (inspection fails) (python 3.9) So it seems to depend on what python is in the EE. if the EE contains python 3.12 it works, 3.8 and 3.9 do not. Notice the OS I'm running on runs 3.12 as well. If I downgrade to ansible-navigator==24.2.0 inspection works for all of the EE's regardless of the python version. Python information by EE: awx-ee:
creator-ee:
ee-29-rhel8:
ee-minimal-rhel8:
ee-supported-rhel8:
|
I can also Confirm this, tested on RHEL 8. |
ISSUE TYPE
SUMMARY
Encountering issue using ansible-navigator to display the Ansible collections within an execution environment:
The environment is Fedora 40, ansible-navigator 24.3.2.
Workaround: downgrade to ansible-navigator 24.2.0.
ANSIBLE-NAVIGATOR VERSION
CONFIGURATION
LOG FILE
STEPS TO REPRODUCE
OS: Fedora 40
EXPECTED RESULTS
I expect to see the list of Ansible collections with their versions.
ACTUAL RESULTS
I receive an error message that something went really wrong, and find the following in the ansible-navigator.log
ADDITIONAL INFORMATION
Only workaround is to downgrade to ansible-navigator 24.2.0
The text was updated successfully, but these errors were encountered: