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.
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:1934
After patching to RHEL 7.3 firewalld restart generates unsupported format character error. The errors should not be there (no error in RHEL 7.2) Error output: Nov 11 16:32:03 brppemail01 firewalld: ERROR: Calling post func <function ifcfg_set_zone_of_interface at 0x25067d0>(('internal', 'ens192')) failed: unsupported format character ':' (0x3a) at index 1 Nov 11 16:32:03 brppemail01 firewalld: ERROR: Calling post func <function ifcfg_set_zone_of_interface at 0x25067d0>(('public', 'ens224')) failed: unsupported format character ':' (0x3a) at index 1 [root@dhcp2-62 ]# cat etc/redhat-release Red Hat Enterprise Linux Server release 7.3 (Maipo) [root@dhcp2-62 ]# [root@dhcp2-62 ]# cat installed-rpms | grep firewalld firewalld-0.4.3.2-8.el7.noarch Fri Nov 11 15:25:34 2016 firewalld-filesystem-0.4.3.2-8.el7.noarch Fri Nov 11 15:24:27 2016 [root@dhcp2-62 ]# [root@dhcp2-62 ]# cat uname Linux brppemail01 3.10.0-327.13.1.el7.x86_64 #1 SMP Mon Feb 29 13:22:02 EST 2016 x86_64 x86_64 x86_64 GNU/Linux [root@dhcp2-62 ]# [root@dhcp2-62 ]# cat etc/sysconfig/network-scripts/ifcfg-ens192 TYPE=Ethernet BOOTPROTO=static IPV4_FAILURE_FATAL=yes NAME=ens192 UUID=c9accfb0-f422-463a-9857-5a24f08ee486 DEVICE=ens192 ONBOOT=yes #DNS1="192.168.18.155" IPADDR=192.168.161.22 PREFIX="24" ZONE=internal check_link_down() { return 1; } [root@dhcp2-62 ]# cat etc/sysconfig/network-scripts/ifcfg-ens224 TYPE="Ethernet" BOOTPROTO="static" DEFROUTE="yes" IPV4_FAILURE_FATAL="yes" IPV6INIT="yes" #IPV6_AUTOCONF="yes" #IPV6_DEFROUTE="yes" #IPV6_FAILURE_FATAL="no" NAME="ens224" UUID="c9accfb0-f422-463a-9857-5a24f08ee486" DEVICE="ens224" ONBOOT="yes" #DNS1="192.168.18.155" IPADDR="10.118.38.136" PREFIX="24" GATEWAY="10.118.38.129" IPV6ADDR="2607:f798:f:e0d::7/64" IPV6_DEFAULTGW="2607:f798:f:e0d::1" #IPV6_PEERDNS="yes" #IPV6_PEERROUTES="yes" #IPV6_PRIVACY="no" [root@dhcp2-62 ]#