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

telco openshift-apiserver panic observed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • None
    • 4.18.0
    • openshift-apiserver
    • Critical
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, importing manifest lists could cause an API crash if the source registry returned an invalid sub-manifest result. With this update, the API flags an error on the imported tag instead of crashing. (link:https://issues.redhat.com/browse/OCPBUGS-49399[*OCPBUGS-49399*])
      ---------
      Before this update, importing manifest lists could cause an API panic if the source registry returned an invalid sub-manifest result (a 500 error, for instance). With this update, the API now flags an error on the tag being imported instead of crashing with a panic.
      Show
      * Previously, importing manifest lists could cause an API crash if the source registry returned an invalid sub-manifest result. With this update, the API flags an error on the imported tag instead of crashing. (link: https://issues.redhat.com/browse/OCPBUGS-49399 [* OCPBUGS-49399 *]) --------- Before this update, importing manifest lists could cause an API panic if the source registry returned an invalid sub-manifest result (a 500 error, for instance). With this update, the API now flags an error on the tag being imported instead of crashing with a panic.
    • Release Note Not Required
    • Done

      This is a clone of issue OCPBUGS-48633. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-45861. The following is the description of the original issue:
      —
      The following test is failing more than expected:

      Undiagnosed panic detected in pod

      See the sippy test details for additional context.

      Observed in 4.18-e2e-telco5g-cnftests/1863644602574049280 and 4.18-e2e-telco5g/1863677472923455488

      Undiagnosed panic detected in pod
{  pods/openshift-kube-apiserver_kube-apiserver-cnfdu3-master-1_kube-apiserver.log.gz:E1202 22:12:02.806740      12 audit.go:84] "Observed a panic" panic="context deadline exceeded" panicGoValue="context.deadlineExceededError{}" stacktrace=<}

      Undiagnosed panic detected in pod
{  pods/openshift-kube-apiserver_kube-apiserver-cnfdu11-master-2_kube-apiserver.log.gz:E1202 22:11:42.359004      14 timeout.go:121] "Observed a panic" panic=<}

              rmarasch@redhat.com Ricardo Maraschini
              openshift-crt-jira-prow OpenShift Prow Bot
              Rahul Gangwar Rahul Gangwar
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: