You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
I encountered an error while running the AWX . The error message indicates that the packages python38-cryptography, python38-pytz, python38-pyyaml, and python38-requests cannot be found. However, the image is based on CentOS 9, where the expected package names should be in the format python3-<package_name>.
Context:
The system is using CentOS 9 as the base OS. According to CentOS 9 conventions, Python 3 packages should be prefixed with python3-, not python38-.
Resolution:
I suggest modifying the dependencies or package names in the AWX to use the correct naming convention (python3-<package_name>). This adjustment should resolve the issue with package dependency resolution.
Action Requested:
Please update the AWX report to reflect the correct package naming convention for CentOS 9. This will ensure compatibility and resolve the dependency resolution error encountered.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered:
Issue:
I encountered an error while running the AWX . The error message indicates that the packages python38-cryptography, python38-pytz, python38-pyyaml, and python38-requests cannot be found. However, the image is based on CentOS 9, where the expected package names should be in the format python3-<package_name>.
Context:
The system is using CentOS 9 as the base OS. According to CentOS 9 conventions, Python 3 packages should be prefixed with python3-, not python38-.
Resolution:
I suggest modifying the dependencies or package names in the AWX to use the correct naming convention (python3-<package_name>). This adjustment should resolve the issue with package dependency resolution.
Action Requested:
Please update the AWX report to reflect the correct package naming convention for CentOS 9. This will ensure compatibility and resolve the dependency resolution error encountered.
Thank you for your attention to this matter.
The text was updated successfully, but these errors were encountered: