Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56244

[4.17] pod(VM) on default network->pod on localnet on same node is broken

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 5
    • None
    • None
    • None
    • None
    • CORENET Sprint 271
    • 1
    • Customer Escalated
    • Done
    • Bug Fix
    • Hide
      * Previously, a pod with an IP address in an `OVN` `localnet` network was unreachable by other pods that ran on the same node but used the default network for communication. Communication between pods on different nodes was not impacted by this communication issue. With this release, communication between a `localnet` pod and a default network pod that both ran on the same node is improved so that this issue no longer exists. (link:https://issues.redhat.com/browse/OCPBUGS-56244[OCPBUGS-56244])
      Show
      * Previously, a pod with an IP address in an `OVN` `localnet` network was unreachable by other pods that ran on the same node but used the default network for communication. Communication between pods on different nodes was not impacted by this communication issue. With this release, communication between a `localnet` pod and a default network pod that both ran on the same node is improved so that this issue no longer exists. (link: https://issues.redhat.com/browse/OCPBUGS-56244 [ OCPBUGS-56244 ])
    • 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:

       

              rravaiol@redhat.com Riccardo Ravaioli
              rhn-support-jortialc Juan Orti
              None
              None
              Yossi Segev Yossi Segev
              None
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: