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 1142741

Summary:	can't add rich rule with port/protocol to zone with non-default target
Product:	Red Hat Enterprise Linux 7	Reporter:	Jiri Popelka <jpopelka>
Component:	firewalld	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED ERRATA	QA Contact:	Tomas Dolezal <todoleza>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	jscotka, pbarta, pvrabec, todoleza
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	noarch
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 12:59:25 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:	1133060

Description Jiri Popelka 2014-09-17 10:25:46 UTC

Description of problem:
Petr Barta noticed that if a zone has a non-default target (e.g. 'drop' zone) then rich rules with 'port' or 'protocol' can't be added.

Steps to Reproduce:
1. firewall-cmd --zone=drop --add-interface=xyz
2. firewall-cmd --zone=drop --add-rich-rule 'rule protocol value="ah" accept'

Actual results:
Error: COMMAND_FAILED: '/sbin/iptables -t filter -A DROP_allow -p ah -m conntrack --ctstate NEW -j ACCEPT' failed: iptables: No chain/target/match by that name.

Expected results:
success

Additional info:
Fixed upstream with
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=e361f33c2bf42acb2e4db578169326b11041b796

Comment 4 errata-xmlrpc 2015-11-19 12:59: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://rhn.redhat.com/errata/RHBA-2015-2422.html