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.
Description of problem:
having ipv6.disabled=1 leads to ERROR level messages in firewalld log (not impacting it's functionality) when using masquerade. unavailable ipv6 procfs path's are causing this error.
Version-Release number of selected component (if applicable):
firewalld-0.7.0-5.el8.noarch
How reproducible:
always
Steps to Reproduce:
boot with ipv6.disabled=1 on kernel cmdline
check `ip -6 a` output to by empty
systemctl restart firewalld
tail -f /var/log/firewalld &
firewall-cmd --add-masquerade
firewall-cmd --state
Actual results:
# firewall-cmd --add-masquerade
2019-08-30 12:09:36 ERROR: Failed to write to file "/proc/sys/net/ipv6/conf/all/forwarding": [Errno 2] No such file or directory: '/proc/sys/net/ipv6/conf/all/forwarding'
success
# firewall-cmd --state
running
Expected results:
ipv6 sysctls not used if ipv6/AF_INET6 is not available.
Additional info:
restart with masquerade in permanent config does not fail to start either though the error is emitted the same.
Upstream:
b28611dee5a2 ("fix: tests: ignore errors about setting ipv6 forwarding")
e9c171d3e1d9 ("fix: tests/regression/gh335: don't set ipv6 sysctls if ipv6 not usable")
f9ede55708e3 ("fix: tests/functions: add macro HOST_SUPPORTS_IPV6")
5605eefb65ad ("test: coverage to make sure masquerade/forward-port only affect IPv4")
816f62a29424 ("fix: nftables: --forward-ports should only affect IPv4")
88e13653686e ("fix: --add-masquerade should only affect ipv4")
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-2020:1836