-
Bug
-
Resolution: Done
-
Major
-
4.17.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
CORENET Sprint 274
-
1
-
Customer Escalated
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
A VM/pod 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. Also, the VM running on node-x is not able to ping the node-X whereas it VM/pod can ping other nodes ?
Version-Release number of selected component (if applicable):
OCP 4.17.34
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. 5. Ping the node on which VM is hosted from VM to check connectivity.
Actual results:
The ping from the VM to other nodes works fine whereas ping to node on which VM is hosted fails.
Expected results:
Ping should always work.
Additional info:
- clones
-
OCPBUGS-56244 [4.17] pod(VM) on default network->pod on localnet on same node is broken
-
- Closed
-
- is depended on by
-
OCPBUGS-59379 pod(VM) on default network->pod on localnet on same node is broken
-
- Closed
-