I see two runs in this report where this showed up in the console-operator log:

• 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/1895026431222616064
• https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.19-e2e-metal-ipi-serial-ovn-dualstack/1895026132575588352

There was another for kube-apiserver here but that looks different. Feel free to redirect if there's a better component for investigating this.

Component Readiness has found a potential regression in the following test:

Undiagnosed panic detected in pod
{  pods/openshift-console-operator_console-operator-97db8d74b-7jfdl_console-operator.log.gz:E0227 09:39:06.998285       1 panic.go:262] "Observed a panic" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<
pods/openshift-console-operator_console-operator-97db8d74b-7jfdl_console-operator.log.gz:E0227 09:39:08.355350       1 panic.go:262] "Observed a panic" panic="runtime error: invalid memory address or nil pointer dereference" panicGoValue="\"invalid memory address or nil pointer dereference\"" stacktrace=<
[...]

Significant regression detected.
Fishers Exact probability of a regression: 99.99%.
Test pass rate dropped from 100.00% to 94.74%.

Sample (being evaluated) Release: 4.19
Start Time: 2025-02-26T00:00:00Z
End Time: 2025-03-05T12:00:00Z
Success Rate: 94.74%
Successes: 54
Failures: 3
Flakes: 0

Base (historical) Release: 4.18
Start Time: 2025-02-03T00:00:00Z
End Time: 2025-03-05T12:00:00Z
Success Rate: 100.00%
Successes: 206
Failures: 0
Flakes: 0

View the test details report for additional context.