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:
When using an OVS interface with a cloned mac of the physical interface of the machine, DHCP uses the wrong MAC address. From my testing the MAC appears to be randomly chosen each time networking is turned off/on. Every once in a while, it will use the correct address.
Version-Release number of selected component (if applicable):
RHCOS 4.6
How reproducible:
At least 50% of the time the wrong MAC is chosen.
Steps to Reproduce:
1. Create connections for configuring OVS with a physical interface attached:
nmcli c add type ovs-bridge conn.interface br-ex con-name br-ex
nmcli c add type ovs-port conn.interface br-ex-port master br-ex con-name ovs-port-br-ex
nmcli c add type ovs-interface slave-type ovs-port conn.interface br-ex-port master ovs-port-br-ex con-name ovs-if-br-ex 802-3-ethernet.cloned-mac-address 52:54:00:16:88:2b
nmcli c add type ovs-port conn.interface ens3 master br-ex con-name ovs-port-phys0
nmcli c add type 802-3-ethernet conn.interface ens3 master ovs-port-phys0 con-name ovs-if-phys0
2. turn off and on networking:
nmcli networking off
nmcli networking on
Actual results:
Random IP is assigned due to unknown MAC being used:
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6508] device[84b7bd5379d23c8f] (br-ex-port): ip4-state: set to 2 (conf)
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6508] device[84b7bd5379d23c8f] (br-ex-port): IPv4 config method is auto
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6509] dbus-object[14f47596016f6ddd]: export: "/org/freedesktop/NetworkManager/DHCP4Config/7"
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6510] device[84b7bd5379d23c8f] (br-ex-port): ipv4.dhcp-client-id: use "mac" client ID: 01:7e:4d:9c:20:dc:f5
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6510] dhcp4: creating IPv4 DHCP client of type NMDhcpNettools
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <info> [1593426822.6511] dhcp4 (br-ex-port): activation: beginning transaction (timeout in 45 seconds)
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6511] dhcp4 (br-ex-port): client-id: set 01:7e:4d:9c:20:dc:f5
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6512] dhcp4 (br-ex-port): dhcp-client4: start 0x55eac96966f0
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6513] device[84b7bd5379d23c8f] (br-ex-port): ip6-state: set to 2 (conf)
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6513] device[84b7bd5379d23c8f] (br-ex-port): IPv6 config method is auto
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6513] device[84b7bd5379d23c8f] (br-ex-port): will enable userland IPv6LL
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6514] platform-linux: link: change 13: user-ipv6ll: set IPv6 address generation mode to none
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6516] platform-linux: do-request-link: 13
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6516] platform-linux: event-notification: RTM_NEWQDISC, flags 0, seq 706: noqueue dev 13 family 0 handle 0 parent ffffffff info 2
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6516] platform: (br-ex-port) signal: qdisc added: noqueue dev 13 family 0 handle 0 parent ffffffff info 2
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6516] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 0: 13: br-ex-port <UP,LOWER_UP;broadcast,multicast,up,running,lowerup> mtu 1500 arp 1 openvswitch* not-init addrgenmode eui64 addr 52:54:00:16:88:2B brd FF:FF:FF:FF:FF:FF rx:0,0 tx:0,0
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6516] platform: (br-ex-port) signal: link changed: 13: br-ex-port <UP,LOWER_UP;broadcast,multicast,up,running,lowerup> mtu 1500 arp 1 openvswitch* not-init addrgenmode eui64 addr 52:54:00:16:88:2B brd FF:FF:FF:FF:FF:FF driver openvswitch rx:0,0 tx:0,0
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6517] device[84b7bd5379d23c8f] (br-ex-port): queued link change for ifindex 13
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593426822.6517] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 0: 13: br-ex-port <UP,LOWER_UP;broadcast,multicast,up,running,lowerup> mtu 1500 arp 1 openvswitch* not-init addrgenmode none addr 52:54:00:16:88:2B brd FF:FF:FF:FF:FF:FF rx:0,0 tx:0,0
Jun 29 10:33:42 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593426822.6517] platform: (br-ex-port) signal: link changed: 13: br-ex-port <UP,LOWER_UP;broadcast,multicast,up,running,lowerup> mtu 1500 arp 1 openvswitch* not-init addrgenmode none addr 52:54:00:16:88:2B brd FF:FF:FF:FF:FF:FF driver openvswitch rx:0,0 tx:0,0
Expected results:
To see DHCP request with MAC: 52:54:00:16:88:2b, which the DHCP server has a static entry for.
Additional info:
Upstream bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/483
I'm not sure if this is related or not, but it may be also using the wrong mac on reboot: https://bugzilla.redhat.com/show_bug.cgi?id=1853750
I tried using the proposed fix here and that did not fix this new bug.
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 (NetworkManager bug fix and enhancement 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/RHBA-2020:4499