The OperatorHub page in the web console is displaying wrong version of my operator if I have installed a previous version of the operator and not the latest.
I installed Knative Serving Operator (0.5.2) in order to perform a rolling upgrade later, but the OperatorHub page at this point already shows the latest available version from the CatalogSource even though it is not installed yet, my steps to reproduce look like this: (and that is the only way I was able to install the previous version and not the latest one from the catalog source):
1) Install CatalogSource from release-v0.6.0 branch of openshift/knative-serving
2) Create knative-serving namespace
3) Install OperatorGroup
4) Install Subscription with:
5) Edit InstallPlan for knative-serving-operator.v0.5.2 and change approved: false -> approved: true (at this point the operator for 0.5.2 is installed)
(right now the OperatorHub in web console incorrectly displays that 0.6.0 is installed)
Attaching a screenshot of OperatorHub after installing 0.5.2 version of my operator. And also a picture of the actual operator that is currently installed.
See https://issues.redhat.com/browse/CONSOLE-1616 for screenshots
Will address next sprint.
Fix in progress, should have a PR up soon.
Checked on ocp 4.6 with payload 4.6.0-0.nightly-2020-09-03-191144.
The latest csv version is v2.0.2, but set currentCSV as v2.0.0
- name: original
- name: stable
Install the couchbase operator, check subscription:
On the installed operators page, for couchbase operator, it shows version v2.0.0.