-
Bug
-
Resolution: Done
-
Normal
-
builds-1.2
-
2
-
False
-
-
False
-
-
Bug Fix
-
Proposed
-
-
-
Builds Sprint #23
-
1
-
PM Sync
Description of problem:
On ROSA clusters, the Shared Resource CSI Driver webhook pods do not deploy.
This does not prevent the creation of Shared Resources - however, because the webhook intercepts all pod `create` calls, this could delay creation of pods by at least 10 seconds.
Additional note from reporter: delay in pod creation is not observed, perhaps because the webhook is "optional" and never gets to a ready state.
Workaround: None
Prerequisites (if any, like setup, operators/versions):
- Builds for OpenShift 1.2
- ROSA cluster using hosted control plane
Steps to Reproduce
Operator reports green/ready, but webhook deployment is not in fact ready.
Webhook pod status reports the following:
status: conditions: - lastProbeTime: null lastTransitionTime: "2024-11-22T17:30:48Z" message: '0/2 nodes are available: 2 node(s) didn''t match Pod''s node affinity/selector. preemption: 0/2 nodes are available: 2 Preemption is not helpful for scheduling.' reason: Unschedulable status: "False" type: PodScheduled phase: Pending
Expected results:
One of the following:
- Operator reports itself "not ready" if any component does not deploy properly
- All Shared Resource CSI driver components deploy properly.
Reproducibility (Always/Intermittent/Only Once):
Always
Acceptance criteria:
Definition of Done:
Build Details:
Builds for OpenShift 1.2.0
ROSA hosted control plane, OCP version 4.17.4
Additional info (Such as Logs, Screenshots, etc):
- is related to
-
BUILD-779 Shipwright Operator reports "Ready" too early
-
- Closed
-
- links to