Bug 1861262 - Operators are not displayed when disconnected filter is applied in OpenShift UI
Summary: Operators are not displayed when disconnected filter is applied in OpenShift UI
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.0
Assignee: Evan Cordell
QA Contact: Jian Zhang
URL:
Whiteboard:
: 1920858 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-28 07:54 UTC by Asheth
Modified: 2023-12-15 18:36 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 19:33:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CVP-2652 0 None None None 2022-03-15 13:35:00 UTC
Red Hat Issue Tracker RFE-1922 0 Medium Backlog Add annotation to operators supported in disconnected environments 2021-07-09 10:22:16 UTC
Red Hat Knowledge Base (Solution) 5320811 0 None None None 2021-07-02 16:31:32 UTC

Description Asheth 2020-07-28 07:54:14 UTC
Description of problem:

As per the documentation link [1], we can select Disconnected from the Infrastructure Feature in the Operator hub to see Operators that work in disconnected environments.

[1] https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.html

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

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

When we check in the OpenShift Web UI, the Infrastructure Feature from the Operator hub shows only two Operators when the disconnected filter is applied.

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

How reproducible:


Steps to Reproduce:
1. Check documentation link--  https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.html
2. Check the list of Operators supported by Red Hat in the Disconnected mode -- https://access.redhat.com/articles/4740011
3. Use OpenShift Web UI. Select Operator Hub -> Infrastructure Feature -> Disconnected

Actual results:
Infrastructure feature shows only two operators when the disconnected filter is applied  
Expected results:
When the disconnected filter is applied, it should show all Red Hat supported Operators, not just two Operators.

Additional info:

Comment 2 Nick Hale 2020-07-28 21:06:13 UTC
Taking a closer look, it seems like the console filters distinguishes the packages that are capable of running on a disconnected cluster by checking for the `operators.openshift.io/infrastructure-features: '["Disconnected"]'` annotation on their PackageManifests. It looks like, as of today, only AMQ Streams and Kafka have this annotation. I'll need to reach out to the remaining operator maintainers to make them aware that this is a requirement for being discovered by console.

Comment 8 jmazzite 2020-10-30 11:24:40 UTC
NOTE: The documentation is not clear in regards to this annotation.

See: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.5/html-single/operators/index#olm-enabling-operator-for-restricted-network_osdk-generating-csvs

It says the following:

====
Look for the Disconnected annotation, which indicates that the Operator works in a disconnected environment:

metadata:
  annotations:
    operators.openshift.io/infrastructure-features: '["Disconnected"]' 
===

But there are annotations in the CSV itself, and there are annotations on the operator Deployment definition (also found in the CSV). I will assume this goes in the CSV top-level metadata.annotation section, NOT the operator Deployment definition.

Can someone:

1) confirm that is where this annotation should go
2) fix the docs to make it more clear :)

Comment 9 Nick Hale 2020-11-17 15:37:07 UTC
> 1) confirm that is where this annotation should go

yes, the annotations should be on the CSV, not the nested deployment spec.

2) fix the docs to make it more clear :)

I'll ask the docs team to make this more explicit.

Comment 11 Evan Cordell 2021-01-15 19:33:49 UTC
For any specific operator that is listed in docs as supporting disconnected, but does not have the proper annotations, please file a bug against that operator specifically. 

I don't think we're getting any value from having an OLM team member review this BZ every other month.

Comment 14 Ben Luddy 2021-01-27 22:08:46 UTC
*** Bug 1920858 has been marked as a duplicate of this bug. ***

Comment 15 Ben Luddy 2021-01-27 22:09:41 UTC
*** Bug 1920999 has been marked as a duplicate of this bug. ***


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