Bug 1920858

Summary: Jaeger operator is not displayed when disconnected mode is selected in the OpenShift Web-Console.
Product: OpenShift Container Platform Reporter: Asheth <asheth>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OperatorHub QA Contact: Jian Zhang <jiazha>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified CC: bluddy, oarribas
Version: 4.6.z   
Target Milestone: ---   
Target Release: ---   
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: 2021-01-27 22:08:46 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:

Description Asheth 2021-01-27 06:53:59 UTC 
Description of problem:

The KCS[1] shows the list of Operators supported by Red Hat in disconnected mode.

[1] https://access.redhat.com/articles/4740011

However, When we check in the OpenShift Web UI, the Infrastructure Feature from the Operator hub shows only 11 Operators when the disconnected filter is applied. The jaeger operator is not displayed.

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

4.6.x

How reproducible:


Steps to Reproduce:

1. Check the list of Operators supported by Red Hat in the Disconnected mode -- https://access.redhat.com/articles/4740011

2. Use OpenShift Web UI. Select Operator Hub -> Infrastructure Feature -> Disconnected


Actual results:
The infrastructure feature does not show Jaeger operator when the disconnected filter is applied  

Expected results:

When the disconnected filter is applied, it should show all Red Hat supported Operators, not just a few Operators. It should show the jaeger operator.


Additional info:

There was a bug opened earlier for this issue "https://bugzilla.redhat.com/show_bug.cgi?id=1861262", however that bug was closed with a note that a separate Bugzilla should be opened for different operators.
Comment 1 Ben Luddy 2021-01-27 22:08:46 UTC 
Please file this with the team that maintains the operator in question: https://bugzilla.redhat.com/show_bug.cgi?id=1861262#c11.

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