In 4.7 and 4.6, we've started seeing this error message in ovs-vswitchd.log: 2020-11-17T12:20:50.895Z|00033|bridge|ERR|interface br-ex: ignoring mac in Interface record (use Bridge record to set local port's mac) This is apparently harmless but it confuses people so we should root it out. I'm pretty sure this is NetworkManager's fault so I'm going to file a bug against them and then this bug can track us getting the fix into RHCOS.
> I'm pretty sure this is NetworkManager's fault so I'm going to file a bug against them and then this bug can track us getting the fix into RHCOS. Ha, nope, figured it out while isolating a reproducer :-)
Verified on 4.8.0-0.nightly-2021-04-06-162113 oc adm node-logs -l kubernetes.io/os=linux -u=ovs-configuration | tee ovs-configuration_service.log 57:Apr 07 12:15:11.534565 ip-10-0-167-47 configure-ovs.sh[1320]: + nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 9001 ipv4.route-metric 100 ipv6.route-metric 100 58-Apr 07 12:15:11.556001 ip-10-0-167-47 configure-ovs.sh[1320]: Connection 'br-ex' (d053f0ed-b619-4b9d-9488-ef6381cb0628) successfully added. 59-Apr 07 12:15:11.573193 ip-10-0-167-47 configure-ovs.sh[1320]: + nmcli connection show ovs-port-phys0 -- 175:Apr 07 12:15:17.713792 ip-10-0-150-215 configure-ovs.sh[1298]: + nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 9001 ipv4.route-metric 100 ipv6.route-metric 100 176-Apr 07 12:15:17.733593 ip-10-0-150-215 configure-ovs.sh[1298]: Connection 'br-ex' (e340078d-c8ed-4460-ba7e-ddb92d362110) successfully added. 177-Apr 07 12:15:17.735709 ip-10-0-150-215 configure-ovs.sh[1298]: + nmcli connection show ovs-port-phys0 -- 242:Apr 07 12:15:19.192439 ip-10-0-248-178 configure-ovs.sh[1306]: + nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 9001 ipv4.route-metric 100 ipv6.route-metric 100 243-Apr 07 12:15:19.206426 ip-10-0-248-178 configure-ovs.sh[1306]: Connection 'br-ex' (c9d08f4e-3c2b-452c-a2b9-f9d9e4a832be) successfully added. 244-Apr 07 12:15:19.208129 ip-10-0-248-178 configure-ovs.sh[1306]: + nmcli connection show ovs-port-phys0 -- 411:Apr 07 12:23:53.132078 ip-10-0-131-216 configure-ovs.sh[1351]: + nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 9001 ipv4.route-metric 100 ipv6.route-metric 100 412-Apr 07 12:23:53.151572 ip-10-0-131-216 configure-ovs.sh[1351]: Connection 'br-ex' (ed6e1280-39fb-4530-816c-5e64d1abff9a) successfully added. 413-Apr 07 12:23:53.156700 ip-10-0-131-216 configure-ovs.sh[1351]: + nmcli connection show ovs-port-phys0 -- 529:Apr 07 12:24:09.130008 ip-10-0-177-87 configure-ovs.sh[1364]: + nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 9001 ipv4.route-metric 100 ipv6.route-metric 100 530-Apr 07 12:24:09.146298 ip-10-0-177-87 configure-ovs.sh[1364]: Connection 'br-ex' (7deb8f10-726f-4b71-a8d9-90f0d0933520) successfully added. 531-Apr 07 12:24:09.151212 ip-10-0-177-87 configure-ovs.sh[1364]: + nmcli connection show ovs-port-phys0 -- 647:Apr 07 12:24:17.252956 ip-10-0-230-107 configure-ovs.sh[1343]: + nmcli c add type ovs-bridge con-name br-ex conn.interface br-ex 802-3-ethernet.mtu 9001 ipv4.route-metric 100 ipv6.route-metric 100 648-Apr 07 12:24:17.270455 ip-10-0-230-107 configure-ovs.sh[1343]: Connection 'br-ex' (70509451-3636-44cc-b6ee-0fd1ca010cca) successfully added. 649-Apr 07 12:24:17.275344 ip-10-0-230-107 configure-ovs.sh[1343]: + nmcli connection show ovs-port-phys0
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438
confirmed with @
confirmed with @rbrattai , we don't need a test case for this.