Bug 1855322 - ppc64le & s390x Operators filtered in Operator Hub for 4.3
Summary: ppc64le & s390x Operators filtered in Operator Hub for 4.3
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.3.z
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ---
: 4.3.z
Assignee: Andy McCrae
QA Contact: Anping Li
URL:
Whiteboard: multi-arch
: 1859316 (view as bug list)
Depends On: 1855316
Blocks: 1859316
TreeView+ depends on / blocked
 
Reported: 2020-07-09 14:46 UTC by Andy McCrae
Modified: 2024-03-25 16:09 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1850546
Environment:
Last Closed: 2020-11-05 20:44:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5312831 0 None None None 2020-08-20 18:02:15 UTC

Description Andy McCrae 2020-07-09 14:46:38 UTC 
+++ This bug was initially created as a clone of Bug #1850546 +++

Description of problem:

Since BZ #1796078 has gone live - the operators that are built and support additional architectures to x86_64 don't show up in OperatorHub because they are missing a label. (per: https://operator-framework.github.io/olm-book/docs/multiarch.html)

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

Currently 3 operators are supported:
cluster-logging-operator
cluster-nfd-operator
elasticsearch-operator

This impacts master all the way to 4.3.

How reproducible:
Consistently.

Steps to Reproduce:
1. On an s390x or ppc64le OCP 4.4+ deploy go to the OperatorHub

Actual results:
No operators are shown.


Expected results:
3 Operators that support ppc64le & s390x are shown.
Comment 2 Alexander Greene 2020-07-15 19:40:04 UTC 
This is not an issue with OLM, I am moving this to Logging.
Comment 3 Jeff Cantrill 2020-07-15 21:01:44 UTC 
@Andy, assigning directly to you to do the backports
Comment 4 Andy McCrae 2020-07-22 13:29:22 UTC 
*** Bug 1859316 has been marked as a duplicate of this bug. ***
Comment 5 Dan Li 2020-07-30 15:35:34 UTC 
*** Bug 1859316 has been marked as a duplicate of this bug. ***
Comment 8 Jeff Cantrill 2020-10-23 15:20:20 UTC 
Setting UpcomingSprint as unable to resolve before EOD
Comment 11 Scott Dodson 2020-11-05 18:18:57 UTC 
Feature enablement after EOL.
Note You need to log in before you can comment on or make changes to this bug.