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.

I recently ran into bug #1074427 when trying to use RHEL7 firewalld inside OpenVZ guest. The OpenVZ kernel is missing the ip6t_rpfilter module which results in firewalld failing before completing initialization, resulting in unreachable machine.

Would it be possible to backport the patch to RHEL7?

Affected version: firewalld-0.3.9-11.el7.noarch

Fixed upstream in 

https://github.com/t-woerner/firewalld/commit/33bf3b95dfaad451645ec274b905fd72e7000729

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

failed firewalld-0.4.3.2-6.el7.noarch (incomplete fix)

the new version (fully) starts only when IndividualCalls=yes option is used

What happens however is disturbing, because the process is running (process list & systemd) but returns --state of 252 - not running. --list-all command succeeds.

iptables-save contains same same rules in both IndividualCalls variants.

Here is an upstream fix:
https://github.com/t-woerner/firewalld/commit/42a997143a5c9c4ff89045752cd7e52e400fd93d

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/RHSA-2016-2597.html