This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2231552 - Race when using DHCP and copy-mac-from
Summary: Race when using DHCP and copy-mac-from
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nmstate
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: NetworkManager Development Team
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-11 20:05 UTC by Ben Nemec
Modified: 2023-08-17 09:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-17 09:58:36 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
NMState config being applied to the nodes (454 bytes, text/plain)
2023-08-11 20:05 UTC, Ben Nemec 		no flags Details
Dnsmasq logs showing requests from different macs (3.11 KB, text/plain)
2023-08-11 20:08 UTC, Ben Nemec 		no flags Details
NM trace logs from a node that changed addresses (9.58 MB, text/plain)
2023-08-11 20:10 UTC, Ben Nemec 		no flags Details
NM trace logs from a node that kept its address (8.53 MB, text/plain)
2023-08-11 20:11 UTC, Ben Nemec 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-715 0 None None None 2023-08-11 20:06:04 UTC
Red Hat Issue Tracker   RHEL-1428 0 None None None 2023-08-17 09:58:35 UTC
Red Hat Issue Tracker RHELPLAN-165686 0 None None None 2023-08-11 20:06:15 UTC

Description Ben Nemec 2023-08-11 20:05:36 UTC 
Created attachment 1983071 [details]
NMState config being applied to the nodes

Description of problem: There seems to be a problem when creating an ovs-bridge with copy-mac-from and assigning its address with DHCP. After rebooting, some of my nodes are requesting an address using a different MAC from the one the bridge was supposed to copy. Others correctly use the copied MAC. In both cases the MAC was set correctly, but it appears there is a timing issue with the DHCP request where sometimes the MAC is set after the request has been sent.

I'm not sure whether this is an NMState issue or a NetworkManager one, but since I can't figure out where NMState is overriding the MAC it's difficult to provide a reproducer for NetworkManager in isolation.


Version-Release number of selected component (if applicable): 2.2.13


How reproducible: About 50% of the time in my experience.


Steps to Reproduce:
1. Apply NMState ovs-bridge config with copy-from-mac set to the underlying physical interface.
2. Reboot node

Actual results: 50% of the nodes will request a DHCP address using the wrong MAC address and get a different IP than they did when NMState initially created the bridge.


Expected results: Nodes all get the same address they had before the reboot.


Additional info: I will attach the NMState YAML and NM trace logs for both a node that did get the same address as well as one that demonstrates the problem.
Comment 1 Ben Nemec 2023-08-11 20:08:08 UTC 
Created attachment 1983072 [details]
Dnsmasq logs showing requests from different macs
Comment 2 Ben Nemec 2023-08-11 20:10:29 UTC 
Created attachment 1983073 [details]
NM trace logs from a node that changed addresses
Comment 3 Ben Nemec 2023-08-11 20:11:11 UTC 
Created attachment 1983074 [details]
NM trace logs from a node that kept its address
Note You need to log in before you can comment on or make changes to this bug.