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 1481207 - Firewall fails to apply when using iptables-services [rhel-7.4.z]
Summary: Firewall fails to apply when using iptables-services [rhel-7.4.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iptables
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Tomas Dolezal
URL:
Whiteboard:
: 1460116 (view as bug list)
Depends On: 1380141 1438937 1477413 1486803 1486871 1544921 1544922 1544923
Blocks: 1399762 1460116 1480374 osp12-automation-blockers
TreeView+ depends on / blocked
 
Reported: 2017-08-14 11:17 UTC by Oneata Mircea Teodor
Modified: 2022-10-18 07:42 UTC (History)
36 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, at boot time or after running the "systemctl restart iptables ip6tables" command, the systemd service was running both iptables and ip6tables services in parallel. Due to the internal locking mechanism that prevented concurrent updates, one of the two services failed to start. This update adds the --wait option to the "iptables-restore" and "ip6tables-restore" commands to make them wait until the lock becomes free, and the described problem no longer occurs.
Clone Of: 1477413
Environment:
Last Closed: 2017-10-19 14:58:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3138851 0 None None None 2017-09-06 12:09:53 UTC
Red Hat Product Errata RHBA-2017:2919 0 normal SHIPPED_LIVE iptables bugfix update 2017-10-19 18:44:49 UTC

Description Oneata Mircea Teodor 2017-08-14 11:17:43 UTC 
This bug has been copied from bug #1477413 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 10 Ihar Hrachyshka 2017-08-22 17:48:21 UTC 
I don't think -17 is affected. We currently experience failures for OpenStack Neutron with -18 with a similar issue; with -17, it passes broken tests just fine.

By the quick look at backported iptables patches, it doesn't seem like xlock was a thing in -17 at all, so you can't possibly get the error there.
Comment 11 Assaf Muller 2017-08-28 13:35:15 UTC 
This is affecting Red Hat OpenStack CI, can we have the latest status here?
Comment 16 Eric Garver 2017-08-30 16:41:15 UTC 
I'm putting this back ON_QA. There is a new bug 1486871 to track the issue found in comment 6.
Comment 17 mathieu bultel 2017-09-06 12:09:53 UTC 
*** Bug 1460116 has been marked as a duplicate of this bug. ***
Comment 22 errata-xmlrpc 2017-10-19 14:58:45 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-2017:2919
Comment 23 Robert Scheck 2017-10-21 23:38:28 UTC 
Obviously, the QA for this update was incomplete, leading to bug #1499367 now.
Note You need to log in before you can comment on or make changes to this bug.