-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
A lot of SyncSets are presenting the following problem, the workaround is to delete theĀ
kubectl.kubernetes.io/last-applied-configuration annotation from the target resource.
failed to apply resource 3: error when applying patch: {"metadata":{"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"operators.coreos.com/v1alpha2\",\"kind\":\"OperatorGroup\",\"metadata\":{\"annotations\":{\"olm.operatorframework.io/exclude-global-namespace-resolution\":\"true\"},\"labels\":{\"hive.openshift.io/managed\":\"true\"},\"name\":\"custom-domains-operator\",\"namespace\":\"openshift-custom-domains-operator\"},\"spec\":{\"targetNamespaces\":[\"openshift-custom-domains-operator\"]}}\n","olm.operatorframework.io/exclude-global-namespace-resolution":"true","olm.providedAPIs":null},"creationTimestamp":null,"generation":null,"resourceVersion":null,"uid":null},"status":null} to: Resource: "operators.coreos.com/v1alpha2, Resource=operatorgroups", GroupVersionKind: "operators.coreos.com/v1alpha2, Kind=OperatorGroup" Name: "custom-domains-operator", Namespace: "openshift-custom-domains-operator" for: "object": error when patching "object": operatorgroups.operators.coreos.com "custom-domains-operator" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update
Done Criteria
- The error doesn't occur anymore