Bug 1804851 - OLM Operators on the OperatorHub page should be filtered by GOOS and GOARCH (openshift-4.4)
Summary: OLM Operators on the OperatorHub page should be filtered by GOOS and GOARCH (...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.4.0
Assignee: bpeterse
QA Contact: Yadan Pei
URL:
Whiteboard:
: 1821318 (view as bug list)
Depends On: 1796078
Blocks: 1796079 1796080 1821318
TreeView+ depends on / blocked
 
Reported: 2020-02-19 18:21 UTC by Samuel Padgett
Modified: 2020-06-04 15:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1796078
Environment:
Last Closed: 2020-05-13 21:59:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4630 0 None closed [release-4.4] Bug 1804851: Filter OLM operators by architecture 2020-07-20 09:36:12 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 21:59:22 UTC

Description Samuel Padgett 2020-02-19 18:21:36 UTC
+++ This bug was initially created as a clone of Bug #1796078 +++

Description of problem:

Not all operators support all architectures.  Therefore, operators under OLM will have an annotation defining supported architectures. If the current architecture of the cluster is not listed in this annotation, the console should filter (hide) the operator from view.  

* The console backend needs to use golang's sys/runtime library to get the architecture of the cluster/pod
* The console should pass the architecture to the front end
* The OLM page should filter based on the provided architecture data.  

This story supports https://issues.redhat.com/browse/OLM-1464

The backend work to gather the architecture & pass to the front end needs backports to 4.3 & 4.2
The front end filtering work needs backports to 4.3, 4.2 if it is clean.

Comment 5 errata-xmlrpc 2020-05-13 21:59:17 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:0581

Comment 6 bpeterse 2020-06-04 15:23:24 UTC
*** Bug 1821318 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.