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

[sig-node] Managed cluster should verify that nodes have no unexpected reboots [Late] [Suite:openshift/conformance/parallel]

Sample (being evaluated) Release: 4.22
Start Time: 2026-01-21T00:00:00Z
End Time: 2026-02-18T12:00:00Z
Success Rate: 97.30%
Successes: 144
Failures: 4
Flakes: 0
Base (historical) Release: 4.21
Start Time: 2026-01-04T00:00:00Z
End Time: 2026-02-03T23:59:59Z
Success Rate: 100.00%
Successes: 175
Failures: 0
Flakes: 0

View the test details report for additional context.

These jobs suffer mass failures, so it's causing a number of regressions, but we're focusing first on why nodes are showing multiple reboots in a non-upgrade job where there should be none.

Appears to be a recent regression, somewhat rare and difficult to reproduce but happening enough to flag CR.

ipv6 jobs do not push cluster/system logs to loki so this is not available for debugging.

Suggest checking journals for the relevant nodes to see why the systems rebooted.

Filed by: dgoodwin@redhat.com