-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Proposed
-
CLOUD Sprint 258
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Component Readiness has found a potential regression in the following test:
operator conditions console
Probability of significant regression: 99.99%
Sample (being evaluated) Release: 4.17
Start Time: 2024-07-18T00:00:00Z
End Time: 2024-07-24T23:59:59Z
Success Rate: 90.00%
Successes: 81
Failures: 9
Flakes: 0
Base (historical) Release: 4.16
Start Time: 2024-05-31T00:00:00Z
End Time: 2024-06-27T23:59:59Z
Success Rate: 100.00%
Successes: 147
Failures: 0
Flakes: 0
There are several install problems on vsphere underway, this one is specific to a case where multiple operators report bad conditions at the end of install, and expending the camgi panel in spyglass, you can see multiple machines showing red because they are stuck in Provisioned state, not Running.
I do not think this is an installer bug at this point, more likely vmware infrastructure. I just don't know what component to file against just yet.
Sample job runs are easy to find in the links above, but here are some examples:
Additional impacted tests:
operator conditions authentication operator conditions cluster-autoscaler operator conditions console operator conditions control-plane-machine-set operator conditions image-registry operator conditions ingress operator conditions kube-controller-manager operator conditions machine-api operator conditions monitoring operator conditions network operator conditions openshift-apiserver operator conditions openshift-samples operator conditions operator-lifecycle-manager-packageserver install should succeed: cluster bootstrap