Closed gonzalomarcote closed 9 months ago
Can you try deleting the operator pod(s)? Deleting them will cause them to restart, and it should detect the CRDs. The CRDs are detected on operator startup.
That was exactly the issue. Restarting cosmos-operator-controller-manager
pods made them to detect recently installed snapshots CRDs.
2023-11-16T10:00:20Z info Requeuing for next snapshot {"controller": "scheduledvolumesnapshot", "controllerGroup": "cosmos.strange.love", "controllerKind": "ScheduledVolumeSnapshot", "ScheduledVolumeSnapshot": {"name":"evm-sidechain-testnet-scheduledvolumesnapshots","namespace":"default"}, "namespace": "default", "name": "evm-sidechain-testnet-scheduledvolumesnapshots", "reconcileID": "b9d9e937-0657-422a-942c-0e8e02e34ef8", "duration": "14m39.235053464s"}
Thanks. You can close this issue
Can you try deleting the operator pod(s)? Deleting them will cause them to restart, and it should detect the CRDs. The CRDs are detected on operator startup.
Thanks for your suggestion, I tried this and also recreated scheduledvolumesnapshot, it's working normally now
When creating one ScheduledVolumeSnapshot I can see it is complaining about missing snapshot CDRs:
The cosmos-operator-system logs say they are not installed:
When those CRDs are installed in our cluster:
Could be this CRDs should be present in the cluster before creating or deploying CosmosFullNode? Or what could be causing this issue?