View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000111||Rocky-Linux-8||ansible-core||public||2022-05-30 09:53||2022-06-22 20:14|
|Reporter||Andrej Radović||Assigned To||Louis Abel|
|Fixed in Version||8.6|
|Summary||0000111: ansible-core-2.12.2-3.1.el8.x86_64 is missing hypothetical `python38-firewall`|
|Description||`ansible-core` used to rely on `python3-firewall` for `firewalld` roles, but since the update to 2.12.2-3.1, it now uses `python38-` packages (since it relies on Python 3.8). Unfortunately, there is no `python38-firewall` package to provide a Python 3.8 version of that `firewalld` binding, so Ansible fails to run any playbook containing firewalld.|
|Steps To Reproduce||1. Update to the latest version of `ansible-core`|
2. Try running any playbook containing `ansible.posix.firewalld`
|Tags||No tags attached.|
|Unfortunately python3-firewall comes from the firewalld package itself. It would make sense in this case why there isn't a python38-firewall package by itself. I don't see any bugs on the red hat bugzilla about this in particular. But we can open one for you.|
|Try setting the var `ansible_python_interpreter` for your playbook to be /usr/bin/python3.6 or /usr/libexec/platform-python for EL 8 systems and let us know if this gets around your issue.|
Louis, please do file this bug upstream if you can, since I don't have a subscription. I think it's reasonable to expect this to work like it did before, with Python packages required for `community.general`, `community.posix`, and such being available in the repo (for the proper Python version).
The `ansible_python_interpreter` setting might be a decent workaround, but I'm going on a vacation today and won't be able to test this until mid-June.
This bug report details part of the issue as described in this bug report. Unfortunately, there are no plans to fix this issue in 2.12 from Red Hat. Instead, the fixes will come when ansible core 2.13 becomes available in RHEL 8.7 and 9.1. However, if you would like to propose a patch to ansible-core 2.12, please do so, and we can see about pushing a new build.
After doing some digging, I attempted a patch to try to resolve the issue in the meantime before ansible core 2.13 is released in upstream.
Can you please test this and let me know how it goes? If it works, we'll push it to our mirrors.
The updated package of ansible-core (ansible-core-2.12.2-3.1.el8.rocky.0.1) should resolve this issue for not only Rocky Linux, but also other rhelish derivatives (such as Oracle, Alma, and so on). As this issue is considered resolved in our testing, we will now close this report.
If there are further issues with ansible-core, please open a new bug report.
|2022-05-30 09:53||Andrej Radović||New Issue|
|2022-05-30 16:16||Louis Abel||Assigned To||=> Louis Abel|
|2022-05-30 16:16||Louis Abel||Status||new => acknowledged|
|2022-05-30 16:16||Louis Abel||Note Added: 0000198|
|2022-05-30 23:16||Louis Abel||Note Added: 0000199|
|2022-05-31 08:45||Andrej Radović||Note Added: 0000200|
|2022-06-22 04:28||Louis Abel||Status||acknowledged => confirmed|
|2022-06-22 04:28||Louis Abel||Note Added: 0000235|
|2022-06-22 05:03||Louis Abel||Status||confirmed => acknowledged|
|2022-06-22 05:03||Louis Abel||Note Added: 0000236|
|2022-06-22 20:14||Louis Abel||Status||acknowledged => closed|
|2022-06-22 20:14||Louis Abel||Resolution||open => fixed|
|2022-06-22 20:14||Louis Abel||Fixed in Version||=> 8.6|
|2022-06-22 20:14||Louis Abel||Note Added: 0000237|