-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.20.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Critical
-
None
-
None
-
None
-
Rejected
-
CLOUD Sprint 278
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Payload 4.20.0-0.nightly-2025-10-12-173250 contains a aggregated-azure-ovn-upgrade-4.20-micro failure due to Undiagnosed panic detected in pod
Typically all panics are treated a blockers until the exposure is understood
Undiagnosed panic detected in pod
{ pods/openshift-cloud-controller-manager_azure-cloud-node-manager-q9vjm_cloud-node-manager_previous.log.gz:E1012 18:39:39.202713 1 runtime.go:142] "Observed a panic" panic="failed to initialize node ci-op-nwkl3117-bb5c4-r5xt9-worker-westus-8x4tc at cloudprovider: failed to set node provider id: failure of getting instance metadata with response \"410 Gone\"" panicGoValue="&fmt.wrapError\{msg:\"failed to initialize node ci-op-nwkl3117-bb5c4-r5xt9-worker-westus-8x4tc at cloudprovider: failed to set node provider id: failure of getting instance metadata with response \\\"410 Gone\\\"\", err:(*fmt.wrapError)(0xc00037fd60)}" stacktrace=<}