Clusterlogging and elasticsearch are not receiving updates when custom catalog source is used

Solution Verified - Updated -

Issue

  • Clusterlogging and elasticsearch operators are not receivingupdates when custom catalog source is used.

  • Different versions of clusterlogging and elasticsearch operators are available on identical RHOCP clusters:

$ oc get csv -n openshift-logging
NAME                                           DISPLAY                            VERSION                 REPLACES                                       PHASE
clusterlogging.4.6.0-202103202154.p0           Cluster Logging                    4.6.0-202103202154.p0   clusterlogging.4.6.0-202103060451.p0           Succeeded
elasticsearch-operator.4.6.0-202103202154.p0   OpenShift Elasticsearch Operator   4.6.0-202103202154.p0   elasticsearch-operator.4.6.0-202103060018.p0   Succeeded

$ oc get csv -n openshift-logging
NAME                                           DISPLAY                            VERSION                 REPLACES                                       PHASE
clusterlogging.4.6.0-202103010126.p0           Cluster Logging                    4.6.0-202103010126.p0   clusterlogging.4.6.0-202102130420.p0           Succeeded
elasticsearch-operator.4.6.0-202103010126.p0   OpenShift Elasticsearch Operator   4.6.0-202103010126.p0   elasticsearch-operator.4.6.0-202102130420.p0   Succeeded
  • Clusterlogging and elasticsearch are not receiving updates even though approval strategy is marked as automatic.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content