Bug 1821580 - Operator Hub Details page shows unstable number of Operators
Summary: Operator Hub Details page shows unstable number of Operators
Keywords:
Status: CLOSED DUPLICATE of bug 1814822
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Cyril
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-07 06:51 UTC by Yadan Pei
Modified: 2020-04-29 19:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-29 19:59:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yadan Pei 2020-04-07 06:51:34 UTC
Description of problem:
When we create catalog source with more than 1 operators, it shows unstable operator number when viewing on Operator Hub Details -> Sources list page

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-04-06-184201

How reproducible:
Always

Steps to Reproduce:
1. create custom catalog source from console(or CLI) using image quay.io/yapei/console-2124:0407
Administration -> Cluster Settings -> Global Configuration -> OperatorHub -> Sources tab -> click 'Create Catalog Source' button ->  set all required fields, set Image (URL of container image) with value quay.io/cajieh/web-console:12.0
2. wait syncing pods running in openshift-marketplace
# oc get catalogsource -n openshift-marketplace
# oc get catalogsource -n openshift-marketplace
NAME                  DISPLAY                                           TYPE   PUBLISHER   AGE
certified-operators   Certified Operators                               grpc   Red Hat     6h20m
community-operators   Community Operators                               grpc   Red Hat     6h20m
custom-console-2124   custom catalog source for console-2124 tetsting   grpc   yapei       91m
redhat-marketplace    Red Hat Marketplace                               grpc   Red Hat     6h20m
redhat-operators      Red Hat Operators                                 grpc   Red Hat     6h20m
# oc get pods -n openshift-marketplace
NAME                                    READY   STATUS    RESTARTS   AGE
certified-operators-58d7c5c95f-fstw6    1/1     Running   0          139m
community-operators-777cf4797b-h8wn2    1/1     Running   0          6h21m
custom-console-2124-ldks7               1/1     Running   0          92m
marketplace-operator-79c94d5cf9-bq96k   1/1     Running   0          6h21m
redhat-marketplace-69c6459cb-jttzv      1/1     Running   0          6h21m
redhat-operators-69874dd8cb-6d4p9       1/1     Running   0          6h21m
3. check which packagemanifest have been synced, we have 3 operator packagemanifests synced which is correct
# oc get packagemanifest | grep 'custom catalog source for console-2124 tetsting'
strimzi-kafka-operator                       custom catalog source for console-2124 tetsting   93m
prometheus                                   custom catalog source for console-2124 tetsting   93m
etcd                                         custom catalog source for console-2124 tetsting   93m                       
4. Check operator number in Operators -> Operator Hub -> Provider Type: Custom
5. Check operator number in Operator Hub Details page, Administration -> Cluster Settings -> Global Configuration -> OperatorHub -> Sources tab

Actual results:
4. In Operator Hub, it shows correct number 3
5. sometimes it shows # of Operators with value 1, sometimes 2, sometimes - 

Expected results:
5. It should show correct operator number in this catalog source, in this case 3 

Additional info:

Comment 1 Samuel Padgett 2020-04-29 19:59:42 UTC
I believe this is a duplicate of bug 1814822 since the operator names are not unique in your custom catalog source.

*** This bug has been marked as a duplicate of bug 1814822 ***


Note You need to log in before you can comment on or make changes to this bug.