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

undiagnosed panic detected (pods/openshift-kube-apiserver)

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • Done
    • Release Note Not Required
    • N/A
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-52410. The following is the description of the original issue:
      —
      https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-ovn-serial-ipv4/1897185389412618240 saw this:

      Undiagnosed panic detected in pod
{  pods/openshift-kube-apiserver_kube-apiserver-master-2_kube-apiserver.log.gz:E0305 11:19:32.272827      14 timeout.go:121] "Observed a panic" panic=<
pods/openshift-kube-apiserver_kube-apiserver-master-2_kube-apiserver.log.gz:E0305 11:19:52.279746      14 timeout.go:121] "Observed a panic" panic=<
pods/openshift-kube-apiserver_kube-apiserver-master-2_kube-apiserver.log.gz:E0305 11:20:12.298745      14 timeout.go:121] "Observed a panic" panic=<}

      The panic may not be the root issue but all panics are considered blockers as the code should be able to handle the condition.

              fbertina@redhat.com Fabio Bertinatto
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Ying Zhou Ying Zhou
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: