RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1758255 - selinux preventing systemd loading iptables module
Summary: selinux preventing systemd loading iptables module
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: selinux-policy
Version: 8.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 8.2
Assignee: Lukas Vrabec
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-03 16:56 UTC by redbugs
Modified: 2020-04-28 16:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:41:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1773 0 None None None 2020-04-28 16:41:38 UTC

Description redbugs 2019-10-03 16:56:40 UTC
When I boot up the system with SElinux in enforcing mode it logs:

[   25.258265] SELinux:  Completing initialization.
[   25.258266] SELinux:  Setting up existing superblocks.
[   25.286457] audit: type=1403 audit(1569965396.755:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
[   25.291758] systemd[1]: Successfully loaded SELinux policy in 975.476ms.
[   25.594651] systemd[1]: Failed to insert module 'ip_tables': Operation not permitted


I'm running a fully updated x86_64 RHEL8 system with
kernel 4.18.0-80.11.2.el8_0
systemd 239-13.el8_0.5
selinux policy targeted-3.14.1-61.el8_0.2


Steps to Reproduce:
1. install Red Hat Enterprise Linux 8
2. register system and load all updates
3. setenforce enforcing
4. reboot

Actual results:
Systemd unable to load iptables module

Expected results:
iptables module loaded

Comment 2 redbugs 2019-10-04 15:54:38 UTC
Downgrading to 

selinux-policy-targeted-3.14.1-61.el8_0.1
selinux-policy-3.14.1-61.el8_0.1

does not resolve the problem.

This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1743758 and https://bugzilla.redhat.com/show_bug.cgi?id=1644805 to me, although I don't have the necessary access to see both of those.

The workaround from #1743758 may be valid, but I have not yet tested.

Comment 16 errata-xmlrpc 2020-04-28 16:41:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1773


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