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

[4.14z] e2e-metal-ipi-ovn fails because of "not enough arguments in call to createServiceForPodsWithLabel" and "undefined: isInterconnectEnabled" compilation errors in ovn-kubernetes tests


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.13, 4.12
    • Moderate
    • No
    • False
    • Hide



      Description of problem

      e2e-metal-ipi-ovn CI jobs fail because of test failures such as the following:

      + go test -timeout=0 -v . -ginkgo.v -ginkgo.focus 'e2e\snon-vxlan\sexternal\sgateway\sthrough\sa\sgateway\spod' -ginkgo.flakeAttempts 2 '-ginkgo.skip=Should validate connectivity before and after deleting all the db-pods at once in Non-HA mode|  e2e br-int NetFlow export validation|disabling egress nodes impeding Legacy health check|Multi Homing|Node IP address migration' -provider skeleton -kubeconfig /root/ovn.conf --num-nodes=2 --report-dir=/root/dev-scripts/ovn-kubernetes/test/_artifacts --report-prefix=control-plane_
      # github.com/ovn-org/ovn-kubernetes/test/e2e [github.com/ovn-org/ovn-kubernetes/test/e2e.test]
      ./e2e.go:1665:113: not enough arguments in call to createServiceForPodsWithLabel
      	have (*framework.Framework, string, number, string, string, map[string]string)
      	want (*framework.Framework, string, int32, string, int32, string, map[string]string)
      ./pod.go:231:11: undefined: isInterconnectEnabled
      ./service.go:364:12: undefined: isInterconnectEnabled
      FAIL	github.com/ovn-org/ovn-kubernetes/test/e2e [build failed]

      This particular failure comes from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_coredns/97/pull-ci-openshift-coredns-release-4.13-e2e-metal-ipi-ovn/1708852351797825536. Search.ci has other similar failures for the periodic-ci-openshift-release-master-nightly-4.13-e2e-metal-ipi-ovn-ipv4 job.

      Version-Release number of selected component (if applicable)

      I have seen this in 4.13 CI jobs.

      How reproducible

      Presently, search.ci shows the following stats for e2e-metal-ipi-ovn jobs the past 14 days:

      Found in 0.27% of runs (0.53% of failures) across 1124 total runs and 113 jobs (50.27% failed)
      periodic-ci-openshift-release-master-nightly-4.13-e2e-metal-ipi-ovn-ipv4 (all) - 2 runs, 100% failed, 100% of failures match = 100% impact
      pull-ci-openshift-coredns-release-4.13-e2e-metal-ipi-ovn (all) - 1 runs, 100% failed, 100% of failures match = 100% impact

      Steps to Reproduce

      1. Post a PR in https://github.com/openshift/coredns against the release-4.13 branch.
      2. Check recent failures of the periodic-ci-openshift-release-master-nightly-4.13-e2e-metal-ipi-ovn-ipv4 job.
      3. Check search.ci using the above link.

      Actual results

      CI fails.

      Expected results

      CI passes, or fails on some other test failure.

            trozet@redhat.com Tim Rozet
            mmasters1@redhat.com Miciah Masters
            Anurag Saxena Anurag Saxena
            0 Vote for this issue
            2 Start watching this issue