Bug 2216520 - Don't install python(3)-firewall it's a dependency of firewalld
Summary: Don't install python(3)-firewall it's a dependency of firewalld
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.3
Assignee: Rich Megginson
QA Contact: Vaclav Danek
URL:
Whiteboard: role:firewall
Depends On:
Blocks: 2216521
TreeView+ depends on / blocked
 
Reported: 2023-06-21 16:32 UTC by Rich Megginson
Modified: 2023-07-18 20:44 UTC (History)
3 users (show)

Fixed In Version: rhel-system-roles-1.22.0-0.13.el9
Doc Type: Bug Fix
Doc Text:
Cause: On RHEL7, when the firewall role is called from another role, and the role is using python3, the firewall role attempts to install the python3 firewall library for that version of python. Consequence: The python3-firewall library is not found and you get an error like "No package matching 'python3-firewall' found available, installed or updated". Fix: Do not explicitly install the python firewall library. Instead, just rely on the correct version being installed when the firewalld package is installed by the firewall role. Result: No errors running against RHEL7.
Clone Of:
: 2216521 (view as bug list)
Environment:
Last Closed:
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles firewall pull 148 0 None Merged fix: Don't install python(3)-firewall it's a dependency of firewalld 2023-06-21 16:44:07 UTC
Red Hat Issue Tracker RHELPLAN-160378 0 None None None 2023-06-21 16:36:50 UTC

Description Rich Megginson 2023-06-21 16:32:48 UTC
When using the firewall role from another role, the firewall role will sometimes try to install the wrong version of python firewall.  Instead, just rely on the firewalld dependency to install it.  https://github.com/linux-system-roles/firewall/pull/148


Note You need to log in before you can comment on or make changes to this bug.