Same issue in 4.5.0-0.nightly-2020-06-10-201008.
There are elasticsearch-operator.4.5.0, but the CSV couldn't be upgraded. That is blocking cluster logging function test and bug verification. $ oc get sub NAME PACKAGE SOURCE CHANNEL elasticsearch-operator elasticsearch-operator qe-app-registry 4.5 $ oc get csv NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.4.4.0-202006080610 Elasticsearch Operator 4.4.0-202006080610 Succeeded $ oc get packagemanifests elasticsearch-operator -o json |jq '.status.channels[].currentCSV' "elasticsearch-operator.4.2.34-202006110619" "elasticsearch-operator.4.2.34-202006110619-s390x" "elasticsearch-operator.4.3.25-202006081335" "elasticsearch-operator.4.4.0-202006080610" "elasticsearch-operator.4.5.0-202006101717" "elasticsearch-operator.4.1.45-202005160309"
Created attachment 1696850 [details] Packagemanifest of elasficseach-operators On the same cluster. I can upgrade elasticsearch-operators from elasticsearch-operator.4.3.25-202006081335 to elasticsearch-operator.4.4.0-202006080610. But when subscribe to 4.5, the CSV bundles weren't updated. Attatched the packagemanifests.
That is cluster logging configuration error. trace in another bug.