Creating execution environment with redhat.satellite collection fails with error [/usr/bin/python3: No module named pip]

Solution Verified - Updated -

Environment

  • AAP 2.5 Latest base image :

    registry.redhat.io/ansible-automation-platform-25/ee-minimal-rhel9:latest
    • AAP 2.6 Latest base image :
    registry.redhat.io/ansible-automation-platform-26/ee-minimal-rhel9:latest

  • ansible-builder 3

Issue

  • When creating execution environment with redhat.satellite collection fails with error :

    /usr/bin/python3: No module named pip
Error: building at STEP "RUN /output/scripts/assemble": while running runtime: exit status 1

Resolution

Ansible Automation Platform 2.5:

  • Set the Python interpreter in dependencies :

    dependencies:
 python_interpreter:
   package_system: python311
   python_path: /usr/bin/python3.11

Ansible Automation Platform 2.6:

  • Set the Python interpreter in dependencies :

    dependencies:
 python_interpreter:
   package_system: python312
   python_path: /usr/bin/python3.12

Root Cause

  • When the Python interpreter is not set to the default Python version 3.11 or 3.12 on the image, Python 3.9 is getting installed and used without installing pip.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments