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

panic in openshift-machine-api_machine-api-controllers pods

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Yes
    • None
    • Approved
    • None
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • None

      (Feel free to update this bug's summary to be more specific.)
      Component Readiness has found a potential regression in the following test:

      Undiagnosed panic detected in pod

      Extreme regression detected.
      Fishers Exact probability of a regression: 100.00%.
      Test pass rate dropped from 100.00% to 84.31%.

      Sample (being evaluated) Release: 4.19
      Start Time: 2025-04-17T00:00:00Z
      End Time: 2025-04-28T23:59:59Z
      Success Rate: 84.31%
      Successes: 43
      Failures: 8
      Flakes: 0

      Base (historical) Release: 4.18
      Start Time: 2025-01-26T00:00:00Z
      End Time: 2025-02-25T23:59:59Z
      Success Rate: 100.00%
      Successes: 107
      Failures: 0
      Flakes: 0

      View the test details report for additional context.

       

      This test details page is showing another variant of panic. It happened in job: periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview. 

       

      Here is an example run: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview/1916216867370831872

       

      Signature:

       

      {  pods/openshift-machine-api_machine-api-controllers-79db86b675-vll87_machineset-controller.log.gz:E0426 21:25:00.904928       1 signal_unix.go:917] "Observed a panic" controller="machineset_controller" object="openshift-machine-api/ms-thin-test" namespace="openshift-machine-api" name="ms-thin-test" reconcileID="2ba01cdd-ad8b-448a-820e-0df0674a0983" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<
pods/openshift-machine-api_machine-api-controllers-79db86b675-vll87_machineset-controller.log.gz:E0426 21:27:01.811260       1 signal_unix.go:917] "Observed a panic" controller="machineset_controller" object="openshift-machine-api/ms-zeroed-test" namespace="openshift-machine-api" name="ms-zeroed-test" reconcileID="02389422-6345-4cda-975f-087e208892ad" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<
pods/openshift-machine-api_machine-api-controllers-79db86b675-vll87_machineset-controller.log.gz:E0426 21:27:15.078773       1 signal_unix.go:917] "Observed a panic" controller="machineset_controller" object="openshift-machine-api/ms-multi-test" namespace="openshift-machine-api" name="ms-multi-test" reconcileID="bff97328-513e-4aca-a63a-64793ba761b9" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<
pods/openshift-machine-api_machine-api-controllers-79db86b675-vll87_machineset-controller.log.gz:E0426 21:28:53.257469       1 signal_unix.go:917] "Observed a panic" controller="machineset_controller" object="openshift-machine-api/ms-thick-test" namespace="openshift-machine-api" name="ms-thick-test" reconcileID="68e1c4bb-0059-44f5-b848-923b6e519db5" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<}

              rh-ee-tbarberb Theo Barber-Bany
              kenzhang@redhat.com Ken Zhang
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: