-
Bug
-
Resolution: Unresolved
-
Normal
-
4.21.0
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
None
-
None
-
None
-
WINC - Sprint 278
-
1
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
The Windows Machine Config Operator fails on startup with a fatal error. The SecretReconciler is unable to retrieve the private key because it attempts to read from the cache before the cache has been started. This occurs during the SetupWithManager call.
How reproducible: Always, on operator startup.
Steps to Reproduce:
Run the operator.
Observe the startup logs.
Actual results: The operator logs a fatal error and exits. The log shows: {"level":"error","ts":"2025-10-06T14:51:29Z","logger":"controllers.secret","msg":"Unable to retrieve private key, please ensure it is created","error":"the cache is not started, can not read objects","stacktrace":"github.com/openshift/windows-machine-config-operator/controllers.(*SecretReconciler).SetupWithManager\n\t/build/windows-machine-config-operator/controllers/secret_controller.go:72..."}
Expected results: The operator should start without error, initialize its cache, and successfully retrieve the private key to begin its reconciliation loop.
Additional info: The error originates in controllers/secret_controller.go at line 72. This suggests a dependency or ordering issue where the reconciler tries to access the cluster before the manager has started the underlying client cache.
- split from
-
OCPBUGS-61369 WMCO crashed during upgrade "Unable to retrieve private key... the cache is not started"
-
- Closed
-
- links to