Bug 1925394

Summary:	Only 12 items of operator appear in operatorhub.
Product:	OpenShift Container Platform	Reporter:	JiwoongYoon <jwyoon>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
OLM sub component:	OperatorHub	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	krizza
Version:	4.6
Target Milestone:	---
Target Release:	---
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-05 14:32:43 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 JiwoongYoon 2021-02-05 05:27:59 UTC

Description of problem:
In a restricted network environment, we installed the mirror registry and Openshift 4.6 version on the s390x equipment as shown in the steps below.
But if you check OperatorHub, you can see only 12 items.
Why is that?

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


How reproducible:


Steps to Reproduce:
1. Configure mirror registry (imageContentSourcePolicy & CatalogSource
Created)
2. Openshift installation complete.
3. deploy imageContentSourcePolicy & CatalogSource
4. Click OperatorHub

Actual results:
Operator Hub shows only 12 items of operator.

Expected results:
All operator images that can be installed on the s390x equipment must be displayed.

Additional info:

Comment 1 JiwoongYoon 2021-02-05 05:30:21 UTC

There are a total of four operator indexes that I added.
1. redhat-operator-index-manifests
2. redhat-marketplace-index-manifest
3. certified-operator-index-manifest
4. community-operator-index-manifest

Comment 2 Kevin Rizza 2021-02-05 14:32:43 UTC

This is explicitly because not all operators are supported on s390x clusters, and in fact most are not. The operatorhub only displays operators supported on the cluster architecture. If there is a specific operator that you are interested in running on a particular architecture, I would recommend reaching out to the owner of that operator and ask for them to explicitly support it.

I'm closing this as NOTABUG because it's up to each individual operator to add support for additional architectures.