-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
RHDG Operator CSV 8.5.7 GA
-
None
-
None
If creating a Cache CR against an Infinispan cluster with cross-site properly configured, if the backup section of the Cache CR lacks a timeout value, the Operator will give a false positive but not create the resource in the cluster.
Example Cache CR:
apiVersion: infinispan.org/v2alpha1
kind: Cache
metadata:
name: resp-cache-multi-cloud
finalizers:
- finalizer.infinispan.org
spec:
clusterName: infinispan
name: respCacheMultiCloud
template: |
replicatedCache:
aliases:
- "0"
backups:
offsite:
backup:
strategy: "SYNC"
(same problem with "ASYNC")
When trying to create that Cache CR, the Operator will update the Cache CR status to ready "True" and the Operator log will show:
2025-04-22T14:32:57.857Z INFO controllers.Cache +++++ Reconciling Cache. {"Request.Namespace": "multi-cloud-demo-app", "Request.Name": "resp-cache-multi-cloud"}
2025-04-22T14:32:57.864Z INFO controllers.Cache ----- End Reconciling Cache. {"Request.Namespace": "multi-cloud-demo-app", "Request.Name": "resp-cache-multi-cloud"}
2025-04-22T14:32:57.864Z INFO controllers.Cache +++++ Reconciling Cache. {"Request.Namespace": "multi-cloud-demo-app", "Request.Name": "resp-cache-multi-cloud"}
2025-04-22T14:32:57.864Z INFO controllers.Cache ----- End Reconciling Cache. {"Request.Namespace": "multi-cloud-demo-app", "Request.Name": "resp-cache-multi-cloud"}
But nothing is logged in the Infinispan Pods of the cluster and nothing is created.
Expected result:
Either create the Cache CR with a default timeout value or fail to reconcile with a returned error in the Cache CR status.
Either outcome should be documented.
