TASK: add python3-libdnf5 to default install for ansible?

[yselkowitz]

What does the ELN SIG need to do?

Following up to the switch to dnf5 (#201), it may be necessary to explicitly add python3 and python3-libdnf5[1] to the ELN installation set, with the exception of -minimal containers (or the like), for the purposes of allowing ansible-driven management in general, as well as package installation in particular, out of the box. While with dnf-4 the presence of python3 and python3-dnf was a given (and similarly with yum before that), with dnf5 (whose implementation is C++) neither can be assumed.

To that end, we need to determine, and then implement as appropriate:

• Which types of images should contain python3 and python3-libdnf5 by default for the purposes of ansible management?
• The ansible.default.dnf5 module was added in ansible-core 2.15. It looks like all supported Fedora versions as well as RHEL/CS 8 and 10 would cover this, but RHEL 9 is still on 2.14. Do we need to include python3-dnf to support that case (or anything else with an old ansible-core)?
• Are there other Python modules that should be present on such images for commonly-used ansible modules?

[1] https://docs.ansible.com/ansible/latest/collections/ansible/builtin/dnf5_module.html

[sgallagher]

@dcantrell Could you help answer some of these questions?

[yselkowitz]

Data:

• The ELN base container image does not even include python3
• The ELN generic cloud image includes python3 but not python3-libdnf5 (nor python3-dnf)
• The "default" custom installation option of ELN with Anaconda includes python3 and python3-dnf (because of subscription-manager, see TASK: Drop remnants of dnf-4 #206) but not python3-libdnf5