[sig-scheduling][Early] The openshift-console console pods [apigroup:console.openshift.io] should be scheduled on different nodes [Suite:openshift/conformance/parallel]

This test fails sometimes on single node upgrades.

In sippy we see it occasionally fail during upgrades when compared to HA sippy link

When looking at a specific job, the failure does seem related to a pod terminating and coming back up, thus the test logic seeing two pods at the same time. Job Link.

Loki query shows a pod coming up and another one soon after around the 3:04 time frame, the events do show a health probe error

A thing to note is that this error does happen more often with the console operator, so we might need to see what we can identify in there in the operator logic.