-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.15.z
-
Quality / Stability / Reliability
-
False
-
-
5
-
None
-
None
-
None
-
None
-
CORENET Sprint 271
-
1
-
Customer Escalated
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
A VM with an IP address in a OVN localnet network is unreachable from other VMs/Pods running in the same node and using the pod network. VMs/Pods running in different nodes work fine.
Version-Release number of selected component (if applicable):
OCP 4.15.21 OCP Virt 4.15.3 Kubernetes NMState Operator 4.15.0-202407101638
How reproducible:
100%
Steps to Reproduce:
1. Create a localnet mapping and net-attach-def: ``` apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: localnet-mappings spec: desiredState: ovn: bridge-mappings: - bridge: br-ex localnet: ovn-localnet-1 state: present ``` ``` apiVersion: k8s.cni.cncf.io/v1 kind: NetworkAttachmentDefinition metadata: name: localnet-network namespace: test spec: config: | { "cniVersion": "0.3.1", "name": "ovn-localnet-1", "type": "ovn-k8s-cni-overlay", "topology": "localnet", "netAttachDefName": "test/localnet-network" } ``` 2. Create a target VM with its only NIC using the test/localnet-network NAD 3. Create a test VM (or pod) with its only NIC in the pod network 4. Ping from the test VM to the target VM. Compare the results from both VMs running in the same node or in different nodes.
Actual results:
The ping from the test VM to the target VM only works if they are in different nodes.
Expected results:
Ping always working.
Additional info:
- depends on
-
OCPBUGS-55016 [4.18] pod(VM) on default network->pod on localnet on same node is broken
-
- Closed
-
- is cloned by
-
OCPBUGS-59246 pod(VM) on default network->pod on localnet on same node is broken
-
- Closed
-
- links to
-
RHBA-2025:9289 OpenShift Container Platform 4.17.34 bug fix update