-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.2, 2.3, 2.4
-
None
-
False
-
-
False
- What is the nature and description of the request?
Include python3-dnf and its dependencies in Ansible supported execution environment, so that ansible-navigator users could run playbooks with ansible.builtin.yum and ansible.builtin.dnf modules inside with the default execution environment (which is the Ansible supported execution environment). - Why does the customer need this? (List the business requirements here)
At present, ansible-navigator users running playbooks with ansible.builtin.yum and ansible.builtin.dnf modules inside with the default execution environment always failed with 'Could not import the dnf python module using /usr/bin/python3.9'. The default execution environment for ansible-navigator at present is registry.redhat.io/ansible-automation-platform-24/ee-supported-rhel8:latest.
The document of ansible.builtin.dnf module has explicitly state the requirement of python-dnf:
Consider that ansible.builtin.yum and ansible.builtin.dnf modules are builtin ansible-core modules so I believe they are downstream supported. I believe the dependencies of these two modules (python3-dnf and its dependencies in this case) should be included in our supported images/execution environments.
- How would you like to achieve this? (List the functional requirements here)
Include python3-dnf and its dependencies in Ansible supported execution environment. The more versions (AAP 2.2 till now, both RHEL 8 and RHEL 9 images) the better. - List any affected known dependencies: Doc, UI etc..
N/A - Github Link if any
N/A