OpenShift cluster will not recognize the new operator versions are available
Issue
- We are trying to upgrade an operator to a higher version, but the installation is looking for a lower version
-
For example, when upgrading the cluster-logging and elsaticsearch operators, the OLM operator shows:
2022-01-14T13:09:36.381982906Z {"level":"error","ts":1642165776.381907,"logger":"controllers.operatorcondition","msg":"Unable to find operatorcondition"
-
Also shows the below on repeat:
2022-01-14T13:15:41.926344032Z time="2022-01-14T13:15:41Z" level=info msg="checking EXAMPLE.5.3.1-12"
-
Finally, it complains about an old version of the operator; the currently installed operator is already higher than this version
"msg":"Unable to find ClusterServiceVersion","request":"example/EXAMPLE.5.1.0-75","error":"ClusterServiceVersion.operators.coreos.com \"EXAMPLE.5.1.0-75\" not found"
-
Used
oc adm mirror
command to generate a new ImageContentSourcePolicy (ICSP) but it does not apply
Environment
- Red Hat OpenShift Container Platform
- 4.8
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.