Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1859316

Summary:	operatorHub shows: ""No operators available There are no operators that match operating system linux and architecture s390x."" even though marketplace/OLM namespace logs show that pkgs/csvs/manifests are found and d'loaded w no issue
Product:	OpenShift Container Platform	Reporter:	milti leonard <mleonard>
Component:	Multi-Arch	Assignee:	Dennis Gilmore <dgilmore>
Status:	CLOSED DUPLICATE	QA Contact:	Barry Donahue <bdonahue>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.3.z	CC:	amccrae, cbaus, dahernan, danili
Target Milestone:	---	Keywords:	Reopened, UpcomingSprint
Target Release:	4.3.z
Hardware:	s390x
OS:	Linux
Whiteboard:	multi-arch
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-30 15:35:34 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:
Bug Depends On:	1855322
Bug Blocks:

Description milti leonard 2020-07-21 17:28:23 UTC

Description of problem:
operatorHub shows: ""No operators available There are no operators that match operating system linux and architecture s390x."" even though marketplace/OLM namespace logs show that pkgs/csvs/manifests are found and d'loaded w no issue

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

How reproducible:
install OCP 4.3 on s390x arch running linuxOS

Steps to Reproduce:
1. install 4.3 on s390x arch running linuxOS
2. check operatorHub for available operators
3.

Actual results:
""No operators available There are no operators that match operating system linux and architecture s390x.""

Expected results:
operators available for install to appear

Additional info:

Comment 1 Carvel Baus 2020-07-22 13:26:58 UTC

We are currently waiting on this functionality to get back ported to 4.3.

Comment 2 Andy McCrae 2020-07-22 13:29:22 UTC


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

Comment 3 milti leonard 2020-07-22 14:49:41 UTC

this is NOT a duplicate of 1855322 which is being restricted to the logging operator. no operators are shown for cluster installed on s390x arch w either 4.3/4.4; this does NOT appear as the case for similar clusters installed w 4.2. operators should at least appear in the operatorHub and error out at install if indeed they do not support the architecture.

i repeat this is NOT s duplicate of 1855322 as it goes beyond the logging operator

Comment 4 Dan Li 2020-07-23 15:16:38 UTC

OperatorHub arch filtering only goes back as far as 4.3, so it would make sense that you don't see it on 4.2. Also, the bug marked as duplicate is assigned to logging component but there are linked PRs for more operators than just logging. We can keep this open but our team thinks BZ 1855322 fixes this bug as well.

Comment 5 Dan Li 2020-07-27 17:50:31 UTC

Adding the label "UpcomingSprint" as blocking bug BZ 1855322 is still WIP and is unlikely to land before next week.

Comment 6 milti leonard 2020-07-29 20:06:01 UTC

@dan thank-you for the response detailing the situation, IF the other BZ will encompass more than just the logging operator, this BZ can be closed as its duplicate. i simply wanted to ensure that my cu situation would be addressed and not overlooked.

again, thank-you

Comment 7 Dan Li 2020-07-30 15:35:34 UTC

Closing this bug as it is a duplicate of 1855322.

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