-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Moderate
-
No
-
False
-
Description of problem:
[sig-scheduling][Early] The openshift-console console pods [apigroup:console.openshift.io] should be scheduled on different nodes [Skipped:SingleReplicaTopology] [Suite:openshift/conformance/parallel]
This test is an infrequent offender of failures in SNO jobs. What is strange is that we were under the impression that it should be skipped when the tests are run in 2 node topologies. Based on conversations with ehila@redhat.com, this test fails because there's an infrequent occurence where a pod is in the middle of being destroyed, but it's compared to the pod coming up and both are determined to be running on the same node.
This seems like an issue with the test as a whole, but the goal of this ticket is to ensure that it is correctly no longer run for SNO.
Example failure
Context thread
- clones
-
OCPBUGS-43928 CI shows ~10% installation failures post boostrap across SNO jobs
- New
- is cloned by
-
OCPBUGS-43936 CI failure: operators should have at least the conditions we had in 4.17
- POST