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

CI got "Undiagnosed panic detected in pod" in openshift-controller-manager because of TypeAssertionError: "interface {} is cache.DeletedFinalStateUnknown, not *v1.BuildConfig"

    XMLWordPrintable

Details

    • Low
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem

      CI failed with a "Undiagnosed panic detected in pod" in openshift-controller-manager/controller-manager:

      {  pods/openshift-controller-manager_controller-manager-7f55874d69-twwz8_controller-manager.log.gz:E0810 16:47:11.628946       1 runtime.go:79] Observed a panic: &runtime.TypeAssertionError{_interface:(*runtime._type)(0x38e6da0), concrete:(*runtime._type)(0x3aa81e0), asserted:(*runtime._type)(0x3d79a20), missingMethod:""} (interface conversion: interface {} is cache.DeletedFinalStateUnknown, not *v1.BuildConfig)
      pods/openshift-controller-manager_controller-manager-7f55874d69-twwz8_controller-manager.log.gz:E0810 16:47:12.630035       1 runtime.go:79] Observed a panic: &runtime.TypeAssertionError{_interface:(*runtime._type)(0x38e6da0), concrete:(*runtime._type)(0x3aa81e0), asserted:(*runtime._type)(0x3d79a20), missingMethod:""} (interface conversion: interface {} is cache.DeletedFinalStateUnknown, not *v1.BuildConfig)}
      

      This particular failure comes from https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-ingress-operator/970/pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-single-node/1689652991788847104; the panic can be seen in openshift-controller-manager_controller-manager-7f55874d69-twwz8_controller-manager.log. Search.ci has other similar failures.

      Version-Release number of selected component (if applicable)

      I have seen this in 4.14 CI jobs.

      How reproducible

      Presently, search.ci shows the following stats for the past two days:

      Found in 0.01% of runs (0.08% of failures) across 45069 total runs and 4901 jobs (17.64% failed)
      pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-single-node (all) - 22 runs, 36% failed, 25% of failures match = 9% impact
      pull-ci-openshift-origin-master-e2e-aws-ovn-single-node (all) - 51 runs, 37% failed, 11% of failures match = 4% impact
      pull-ci-openshift-cluster-ingress-operator-master-e2e-aws-ovn-single-node (all) - 7 runs, 57% failed, 25% of failures match = 14% impact
      periodic-ci-openshift-release-master-ci-4.14-e2e-gcp-ovn-upgrade (all) - 74 runs, 32% failed, 4% of failures match = 1% impact
      

      Search.ci times out if I try to search for older job runs.

      Steps to Reproduce

      1. Check search.ci using the link above.

      Actual results

      CI fails.

      Expected results

      CI passes, or fails on some other test failure.

      Attachments

        Activity

          People

            cdaley Corey Daley
            mmasters1@redhat.com Miciah Masters
            Jitendar Singh Jitendar Singh
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: