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

[4.11] ovnkube-trace does wrong validation for outport on shared gateway

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.11.0
    • None
    • SDN Sprint 228, SDN Sprint 229
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Whenever one runs ovnkube-trace from an in-cluster pod to a pod in the host network that is in different node, the following spurious error appears despite of the underlying ovn-trace being correct:
      
      ovn-trace indicates failure from ingress-canary-7zhxs to router-default-6758fb465c-s66rv - output to "k8s-worker-0.example.redhat.com" not matched
      
      This is caused because as per[1], if the destination pod is in host network, the outport is expected to be of the form "k8s-${NODE_NAME}", which is true only if either in local gateway or if the source pod is in the same node than the destination pod.
      
      This is already fixed in the master branch[2], but we would need this to be backported to previous releases. 
      

      Version-Release number of selected component (if applicable):

      4.11.4
      

      How reproducible:

      Always
      

      Steps to Reproduce:

      1. ovnkube-trace from pod in the SDN to pod in host network
      2.
      3.
      

      Actual results:

      Wrong error
      

      Expected results:

      No wrong error
      

      Additional info:

      References:
      [1] - https://github.com/openshift/ovn-kubernetes/blob/release-4.11/go-controller/cmd/ovnkube-trace/ovnkube-trace.go#L771-L777
      [2] - https://github.com/openshift/ovn-kubernetes/blob/master/go-controller/cmd/ovnkube-trace/ovnkube-trace.go#L755-L769
      

            akaris@redhat.com Andreas Karis
            rhn-support-palonsor Pablo Alonso Rodriguez
            Anurag Saxena Anurag Saxena
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: