-
Bug
-
Resolution: Done
-
Blocker
-
None
-
False
-
False
-
Quay Enterprise
-
?
-
Undefined
-
The current catalog source only lists two operator images: Quay 3.4.5 and 3.5.1.
root@quay:~/openshift-4# oc project openshift-marketplace Now using project "openshift-marketplace" on server "https://api.openshift.ibazulic.me:6443". root@quay:~/openshift-4# oc get pods NAME READY STATUS RESTARTS AGE 46d4853e15d0f39a4313044e8e6bc6dc601597012c1c02d069f0cc56b5qdhbg 0/1 Completed 0 7d1h certified-operators-mrsln 1/1 Running 0 6m28s community-operators-c8cqd 1/1 Running 0 70m marketplace-operator-7b5574477c-ng8qx 1/1 Running 0 8d redhat-marketplace-q74sd 1/1 Running 0 8d redhat-operators-xsg9k 1/1 Running 0 21h root@quay:~/openshift-4# oc cp redhat-operators-xsg9k:/database/index.db index.db tar: Removing leading `/' from member names root@quay:~/openshift-4# sqlite3 index.db SQLite version 3.27.2 2019-02-25 16:06:06 Enter ".help" for usage hints. sqlite> SELECT name, bundlepath, skips, skiprange, replaces FROM "main"."operatorbundle" WHERE "name" LIKE '%quay-operator%'; quay-operator.v3.5.1|registry.redhat.io/quay/quay-operator-bundle@sha256:831f385afdd3f1fdd56175d41849dee9688527f51fddbde05064725d649389b7||>=3.4.x <3.5.1| quay-operator.v3.4.5|registry.redhat.io/quay/quay-operator-bundle@sha256:f27ab820209a963e1863f39e0c2ce3b8b289a996fc5f594097cb9f9ad25890c8||>=3.3.x <3.4.5|
This is not true for other projects who have more operator versions and sometimes even multiple operators that differ only in their z-stream, for example:
sqlite> SELECT name, bundlepath, skips, skiprange, replaces FROM "main"."operatorbundle" WHERE "name" LIKE '%rhsso%'; rhsso-operator.7.4.1|registry.redhat.io/rh-sso-7-tech-preview/sso74-rhel8-operator-bundle@sha256:6c405f51d712ac8952c30d8e97aaef15f9cdf73061c6014b6d9b11c080fe1a04|||rhsso-operator.7.4.0 rhsso-operator.7.4.0|registry.redhat.io/rh-sso-7-tech-preview/sso74-rhel8-operator-bundle@sha256:1a7e24f1d76e670b32b19fa34deb48c27ae75757249e1dce0ef6515cf29cab46||| rhsso-operator.7.4.7|registry.redhat.io/rh-sso-7-tech-preview/sso74-rhel8-operator-bundle@sha256:39b8963c60aebbb8191ccd75f5fe2fcb701ec348a6eeec2ace9ac19ff1da33e1|||rhsso-operator.7.4.1 sqlite>
Because some customers cannot, on a whim, update Quay in their clusters before testing the upgrade first, having multiple versions of the operator in the catalog source enables them to deploy a desired version of Quay, one that they tested in their env.
Please check!
- is related to
-
PROJQUAY-2098 Fix Operator update graph to avoid previous z-streams from getting truncated
- Closed
- relates to
-
PROJQUAY-2910 Quay operator specific release versions install/upgrade paths
- Closed