This article explains a failure encountered during the upgrade of the Vertica Operator from version 25.1.0-0 to 25.2.1-0. The issue was caused by a cache sync error and Helm chart misconfiguration, resulting in the Operator Manager entering a CrashLoopBackOff state.
Environment
- Vertica Operator
- Kubernetes
- Helm chart (custom, non-official)
- Vertica version 25.1.0-0 → 25.2.1-0
- Upgrade procedure from Vertica documentation
Situation
During the upgrade of the Vertica Operator, the Operator Manager pod failed with the following error:
ERROR setup problem running manager
{"error": "failed to wait for verticareplicator caches to sync: timed out waiting for cache to be synced for Kind *v1beta1.VerticaReplicator"}The pod entered a CrashLoopBackOff state, and the database was unexpectedly brought down.
