Bug 1820019

Summary: OperatorHub shows old 3scale-operator version
Product: OpenShift Container Platform Reporter: Takayuki Konishi <tkonishi>
Component: Management ConsoleAssignee: Yadan Pei <yapei>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 4.2.0CC: aos-bugs, jokerman, jonjacks, nmukherj, spadgett, yapei
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:25:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
3scale-operator 0.3.0
none
3Scale v0.5.1 none

Description Takayuki Konishi 2020-04-02 05:26:17 UTC
Created attachment 1675604 [details]
3scale-operator 0.3.0

Description of problem:
On OpenShift web console of an OCP cluster, OperatorHub shows an old version of 3scale-operator. The latest version is 0.5.0, but 0.3.0 on OperatorHub. It seems not to be updated since it fetched the first time. The installed operator is the latest version. So this issue is only on OperatorHub UI.

Version-Release number of selected component (if applicable):

OpenShift 4.2(CRC)
kubernetes v1.14.6+a8d983c

How reproducible:
Unclear. When I create a new OCP cluster, it shows the latest version of 3scale-operator. It seems not to be updated since it fetched the first time.

Actual results:
OperatorHub shows 3scale-operator 0.3.0 (see the attached 3scale-operator030.png)

Expected results:
OperatorHub shows the latest 3scale-operator

Additional info:

Comment 1 Samuel Padgett 2020-04-06 12:24:38 UTC
Jon, is this the same problem as bug 1764540?

Comment 2 Jon Jackson 2020-05-07 19:31:26 UTC
Just checked 4.5 and the latest version of 3scale seems to be showing accurately now.

Comment 3 Jon Jackson 2020-05-07 19:33:19 UTC
As Sam pointed out, this was likely the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1764540 which was resolved by https://github.com/openshift/console/pull/3536

Comment 4 Yadan Pei 2020-05-08 09:13:14 UTC
Created attachment 1686404 [details]
3Scale v0.5.1

1. Check default channel and version for 3scale-community-operator
# oc rsh -n openshift-marketplace community-operators-54dbf9656b-2rmqh
sh-4.2cd downloaded/
sh-4.2$ cat 3scale-community-operator.package.yaml 
packageName: 3scale-community-operator
channels:
  - name: threescale-2.6
    currentCSV: 3scale-community-operator.v0.3.0
  - name: threescale-2.7
    currentCSV: 3scale-community-operator.v0.4.0
  - name: threescale-2.8
    currentCSV: 3scale-community-operator.v0.5.1
defaultChannel: threescale-2.8

Default channel for 3scale-community-operator is threescale-2.8 & v0.5.1

2. Check 3scale-community-operator in Operator Hub, it is v0.5.1

Verified on 4.5.0-0.nightly-2020-05-07-144853

Comment 7 errata-xmlrpc 2020-07-13 17:25:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409