Bug 1852106
| Summary: | NM OVS: DHCP occurs with incorrect MAC | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Tim Rozet <trozet> | |
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 8.2 | CC: | acardace, atragler, bgalvani, dcbw, lrintel, rkhan, sukulkar, thaller, till, toneata, vbenes | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | 8.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | NetworkManager-1.26.0-0.2.1.el8 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1857775 (view as bug list) | Environment: | ||
| Last Closed: | 2020-11-04 01:50:15 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1857775 | |||
|
Description
Tim Rozet
2020-06-29 18:15:08 UTC
Note in addition to this behavior. I also see that even the interface sometimes gets the wrong mac address:
[core@test-q9gz9-bootstrap ~]$ ip a show br-ex
30: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether e2:e4:16:ac:b0:4c brd ff:ff:ff:ff:ff:ff
inet 192.168.126.108/24 brd 192.168.126.255 scope global dynamic noprefixroute br-ex
valid_lft 2779sec preferred_lft 2779sec
inet6 fe80::83cc:2a30:8324:9b41/64 scope link noprefixroute
valid_lft forever preferred_lft forever
The above interface got e2:e4... however:
[core@test-q9gz9-bootstrap ~]$ nmcli conn show ovs-if-br-ex | grep mac-address
802-3-ethernet.mac-address: --
802-3-ethernet.cloned-mac-address: 52:54:00:16:88:2B
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist: --
and in OVS:
[core@test-q9gz9-bootstrap ~]$ sudo ovs-vsctl list interface
_uuid : 78972a20-99f7-4b26-84fb-7c11d1eb2e82
admin_state : up
bfd : {}
bfd_status : {}
cfm_fault : []
cfm_fault_status : []
cfm_flap_count : []
cfm_health : []
cfm_mpid : []
cfm_remote_mpids : []
cfm_remote_opstate : []
duplex : []
error : []
external_ids : {NM.connection.uuid="e999d8ab-c997-4056-b80d-5992d907e17e"}
ifindex : 30
ingress_policing_burst: 0
ingress_policing_rate: 0
lacp_current : []
link_resets : 3
link_speed : []
link_state : up
lldp : {}
mac : "52:54:00:16:88:2B"
mac_in_use : "e2:e4:16:ac:b0:4c"
mtu : 1500
mtu_request : []
name : br-ex
Jun 29 13:46:29 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593438389.2835] dbus-object[965b92ce33c5de54]: export: "/org/freedesktop/NetworkManager/DHCP4Config/17"
Jun 29 13:46:29 test-q9gz9-bootstrap NetworkManager[32858]: <debug> [1593438389.2836] device[c571e98b3b7fe327] (br-ex): ipv4.dhcp-client-id: use "mac" client ID: 01:e2:e4:16:ac:b0:4c
Jun 29 13:46:29 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593438389.2836] dhcp4: creating IPv4 DHCP client of type NMDhcpNettools
Jun 29 13:46:29 test-q9gz9-bootstrap NetworkManager[32858]: <info> [1593438389.2836] dhcp4 (br-ex): activation: beginning transaction (timeout in 45 seconds)
Jun 29 13:46:29 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593438389.2836] dhcp4 (br-ex): client-id: set 01:e2:e4:16:ac:b0:4c
Jun 29 13:46:29 test-q9gz9-bootstrap NetworkManager[32858]: <trace> [1593438389.2837] dhcp4 (br-ex): dhcp-client4: start 0x55eac968c130
Upstream merge request: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/557 The fix looks to be working. I tried configuring a bunch of times and nmcli networking off/on and it seems to be OK. 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. *** Bug 1853750 has been marked as a duplicate of this 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 |