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:
I can see a ZONE_CONFLICT error in logs sporadically but reproducibly after service firewalld restart, adding connection with autoconnect yes and then modifying it while NM auto connecting it.
Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.1-19.git20140326.4dba720.el7_0.x86_64
How reproducible:
once in 50 cases. have beaker job that catches it everytime.
Steps to Reproduce:
1.restart firewalld service
2.nmcli connection add type ethernet ifname eth0 con-name ethie
3.nmcli connection edit ethie
4.set connection.zone drop
5.nmcli connection up id ethie
6.check zone via firewall-cmd --zone=drop --list-all
Actual results:
sometimes there is ZONE_CONFLICT in logs and device not added to desired zone
Expected results:
no conflict, device correctly in the desired zone
Additional info: