Bug 1804851

Summary:	OLM Operators on the OperatorHub page should be filtered by GOOS and GOARCH (openshift-4.4)
Product:	OpenShift Container Platform	Reporter:	Samuel Padgett <spadgett>
Component:	Management Console	Assignee:	bpeterse
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, bpeterse, jokerman, spadgett, yapei
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1796078	Environment:
Last Closed:	2020-05-13 21:59:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1796078
Bug Blocks:	1796079, 1796080, 1821318

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. ***