Bug 2007367
| Summary: | Hybrid overlay wipes network interface static IP configuration in favor of DHCP | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sebastian Soto <ssoto> |
| Component: | Networking | Assignee: | Sebastian Soto <ssoto> |
| Networking sub component: | ovn-kubernetes | QA Contact: | Anurag saxena <anusaxen> |
| Status: | CLOSED NOTABUG | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | aos-bugs, bpickard, team-winc, trozet |
| Version: | 4.9 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-12 22:30:38 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: | |||
This is happening due to the hybrid-overlay. Assigning it to the SDN team. Hybrid overlay should be aware of IP Address configurations and maintain those configurations when creating the vEthernet adapter. Created upstream issue https://github.com/ovn-org/ovn-kubernetes/issues/2530 This issue is fixed in Windows Server 2022. In previous versions of Windows Server it can be resolved by disabling deviceless NICs: New-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Services\hns\State -Name DeviceLessNicDisabled -PropertyType DWORD -Value 1 Looks like this is not a bug in ovn-kube and resolved by a Windows fix. Closing. |
Description of problem: Attempting to configure a Windows VM set up with a static IP results in the configuration failing after hybrid-overlay.exe is started. The VM will show up as a node object but will not be in a usable state. The static IP is removed, and a new IP will be given by DHCP. Before WMCO configures: ``` $ ipconfig /all Ethernet adapter Ethernet0: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter Physical Address. . . . . . . . . : 00-50-56-AC-49-9D DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::e952:a612:4677:d362%3(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.29.15(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.224 Default Gateway . . . . . . . . . : 192.168.29.1 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled ``` After: ``` $ ipconfig /all Ethernet adapter vEthernet (Ethernet0): Connection-specific DNS Suffix . : us-west-2.compute.internal Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2 Physical Address. . . . . . . . . : 00-50-56-AC-49-9D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d881:91e:30e2:130f%8(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.29.14(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.224 Lease Obtained. . . . . . . . . . : Thursday, September 23, 2021 6:26:57 PM Lease Expires . . . . . . . . . . : Friday, September 24, 2021 6:26:57 PM Default Gateway . . . . . . . . . : 192.168.29.1 DHCP Server . . . . . . . . . . . : 100.96.1.1 DHCPv6 IAID . . . . . . . . . . . : 134238294 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-DE-54-B2-00-50-56-AC-49-9D DNS Servers . . . . . . . . . . . : 10.0.0.2 NetBIOS over Tcpip. . . . . . . . : Enabled ``` Note that the IP has changed and DHCP is enabled. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Disable DHCP on the Windows VM's network interface and add a static IP: # find index of interface Get-NetIPInterface #disable dhcp Set-NetIPInterface -Ifindex $INDEX -Dhcp disabled # Interface should have some different IP now, remove it so we can create a new one Remove-NetIPAddress -InterfaceIndex $INDEX -IPAddress $IP # Create static IP New-NetIPAddress -InterfaceIndex $INDEX -IPAddress $NEW_IP -PrefixLength $PREFIX_LENGTH -DefaultGateway $SUBNET_GATEWAY 2. Attempt to configure the VM using the new IP by adding it to the windows-instance configmap. Actual results: Windows node is not fully configured. Static IP configuration is removed and the VM has an IP given by DHCP. Expected results: Windows node is fully configured. Static IP remains what it was before configuration. Additional info: