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

4.17-upgrade-from-stable-4.16-e2e-metal-ipi-ovn-upgrade job fails with v6 tests erroring out on a v4 CI lane.

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None

      Skip certain networking tests that are v6 only on v4 CI lanes.

      This job is failing at approx 75% rate. We noticed it because it is causing the component readiness
      dashboard to flag test cases as regressions. It's likely not a regression and just that component readiness
      has no 4.16 job to compare against. There is a slack thread started to discuss this part of it.

      This bug is to address the actual failures in the job

      At first glance, looking at the intervals pane of a a few failed jobs they all seem clumped together and they are
      all networking related. Tests are run in parallel and possibly something is mucking up networking for a brief
      period which causes these to fail in the same window.

      [sig-network] Internal connectivity for TCP and UDP on ports 9000-9999 is allowed [Serial:Self] [Suite:openshift/conformance/parallel]
      [sig-network] network isolation when using a plugin in a mode that does not isolate namespaces by default should allow communication between pods in different namespaces on the same node [Suite:openshift/conformance/parallel]
      [sig-network] services basic functionality should allow connections to another pod on a different node via a service IP [Suite:openshift/conformance/parallel]
      [sig-network] services when using a plugin in a mode that does not isolate namespaces by default should allow connections to pods in different namespaces on the same node via service IPs [Suite:openshift/conformance/parallel]
      [sig-network][Feature:EgressRouterCNI] should ensure ipv4 egressrouter cni resources are created [apigroup:operator.openshift.io] [Suite:openshift/conformance/parallel]
      [sig-network] external gateway address when using openshift ovn-kubernetes should match the address family of the pod [Suite:openshift/conformance/parallel]
      [sig-network][Feature:EgressFirewall] when using openshift ovn-kubernetes should ensure egressfirewall is created [Suite:openshift/conformance/parallel]
      [sig-network][Feature:EgressRouterCNI] when using openshift ovn-kubernetes should ensure ipv6 egressrouter cni resources are created [apigroup:operator.openshift.io] [Suite:openshift/conformance/parallel]
      [sig-network-edge][Feature:Idling] Unidling [apigroup:apps.openshift.io][apigroup:route.openshift.io] should work with TCP (when fully idled) [Suite:openshift/conformance/parallel]
      [sig-network-edge][Feature:Idling] Unidling [apigroup:apps.openshift.io][apigroup:route.openshift.io] should work with UDP [Suite:openshift/conformance/parallel]

              jluhrsen Jamo Luhrsen
              jluhrsen Jamo Luhrsen
              Anurag Saxena Anurag Saxena
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: