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.

see: https://bugzilla.redhat.com/show_bug.cgi?id=1378693

It appears that iptables-services includes the following:
```
if [ $1 -ge 1 ] ; then # Package upgrade, not uninstall
   /bin/systemctl try-restart iptables.service >/dev/null 2>&1 || :
   /bin/systemctl try-restart ip6tables.service >/dev/null 2>&1 || :
fi
```

Problem is that OpenShift runs a daemon that dynamically add/removes iptables rules at run time. If one then updates iptables-services the run time rules get deleted. Since these added rules are dynamic they should not be saved and restored on reboot (or across restart)

We have to tell customers to update iptables-services, which will break all of their traffic, then they have to restart docker, then they have to restart kubernetes/OpenShift.

Why does iptables-services include the restart at all? It seems that it should be removed from the --scripts entirely...

Why is OpenShift not able to cope with core service restarts? This really seems like an OpenShift (dependency) specific issue. 

Is it possible for OpenShift to provide systems scripts/triggers that could combat this? IE: Watch for restarts in iptables, and restart docker/openshift?

OpenShift could likely add some sort of trigger to restart when iptables-services is restarted. But it doesn't change the fact that iptables-services may not need to restart on update at all.

There has not been a change in the spec file of iptables since RHEL-7.0 regarding the services sub package.

There is this since 1.4.21-5 (Jan 15 2014):

%postun services
/sbin/ldconfig
%systemd_postun_with_restart iptables.service ip6tables.service

I agree though that the use of "_with_restart" might not be good.

This has not been introduced with 7.3 - it is there since 7.0.

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/RHEA-2018:0715