-
Notifications
You must be signed in to change notification settings - Fork 109
OLM cannot update memcached operator CSV #31
Comments
Looks like "status" field is missing from CSV spec. I can't find similar field here: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/deploy/chart/catalog_resources/rh-operators/etcdoperator.v0.9.2.clusterserviceversion.yaml as well. |
I removed subresource from updatestatus call -- And then it started working. |
Another issue is that the CSV specifies policyrule as '*' for API groups, resources and verbs while the operator creates a finer RBAC policy for memcached-operator. They don't match and CSV remains in pending state. |
Does the issue resolved? It also happend to me, error log from olm-operator:
2)time="2019-02-20T06:59:38Z" level=warning msg="installmodes not supported" csv=memcachedoperator.v0.0.1 err="SingleNamespace InstallModeType not supported, cannot configure to watch one namespace" namespace=olm opgroup=olm-operators phase=
3)time="2019-02-20T07:13:35Z" level=info msg="requirements were not met" csv=memcachedoperator.v0.0.1 namespace=olm phase=Pending
So how do I modify the policyrule? I tried many policyrule configuration, but all failed. Can anybody help? Thanks~ |
The OLM steps in the Getting Started as its example was updated in the #57 in order to address this issue as well. Then, I am closing this task. However, please, feel free to re-open if you see that still required. |
I followed guides to deploy upstream olm on minikube. Then created a memcached operator. I applied the CRD and role, sa and sa-binding from deploy directory of memcached scaffold.
Now, OLM cannot update CSV status with error:
level=info msg="error updating ClusterServiceVersion status: the server could not find the requested resource (put clusterserviceversions.operators.coreos.com memcachedoperator.v0.0.1)" csv=memcachedoperator.v0.0.1 namespace=default phase=
Strange thing is, it can list the CSVs using same client and that list contains memcachedoperator
The text was updated successfully, but these errors were encountered: