Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1520534

Summary: iptables-services: restarting services unloads unrelated kernel modules
Product: Red Hat Enterprise Linux 7 Reporter: Eric Garver <egarver>
Component: iptablesAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: Tomas Dolezal <todoleza>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.4CC: amuller, atragler, danw, iptables-maint-list, jmaxwell, todoleza
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: iptables-1.4.21-29.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 13:06:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1654714    

Description Eric Garver 2017-12-04 16:25:59 UTC
As reported in bug 1512575 when the iptables-services package is upgraded it will do a full restart and recursively unload kernel modules. This causes a problem for other packages that may be using those modules or modules that depend upon them.

e.g.
  nf_conntrack.ko used by openvswitch.ko
  vport-geneve.ko used by openvswitch.ko
  geneve.ko used by vport-geneve.ko

iptables-services restart will attempt to recursively unload nf_conntrack and therefore also openvswitch, vport-geneve, geneve. This will cause openvswitch tunnels to go down.

iptables-services stop/restart should _not_ be unloading nf_conntrack and related kernel modules.

Comment 2 Phil Sutter 2017-12-12 16:12:14 UTC
The whole concept of unloading netfilter modules upon service restart seems futile to me. So far I heard two reasons for it being done:

1) Reset kernel state (esp. regarding conntrack).
2) Get conntrack out of fast path for increased performance.

Both aspects could be dealt with by either manually unloading modules (for users who know what they do) or a simple reload after disabling iptables (or configuring it into a stateless firewall).

Getting rid of module unloading altogether would also allow to drop previous workarounds for problems this caused (e.g. bug 1486803).

Comment 4 Phil Sutter 2018-05-07 10:36:05 UTC
Targeting at RHEL7.6 for now, including RHEL7.5 z-stream.

Comment 9 Phil Sutter 2019-03-15 18:29:12 UTC
Removing z-stream requests at least for now to prevent automatic ticket cloning.

Comment 15 errata-xmlrpc 2019-08-06 13:06:28 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-2019:2218