Bug 1787358 - Operator Hub shows many operators that are not built for s390
Summary: Operator Hub shows many operators that are not built for s390
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Multi-Arch
Version: 4.2.z
Hardware: s390x
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Andy McCrae
QA Contact: Barry Donahue
URL:
Whiteboard:
Depends On:
Blocks: OCP/Z_4.2
TreeView+ depends on / blocked
 
Reported: 2020-01-02 14:37 UTC by Tom Dale
Modified: 2020-06-02 18:42 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-02 18:42:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Red Hat Provided (671.24 KB, image/png)
2020-01-03 22:08 UTC, Cheryl A Fillekes
no flags Details
Screen Shot of Operator Hub today (124.77 KB, image/png)
2020-01-28 23:57 UTC, Cheryl A Fillekes
no flags Details

Description Tom Dale 2020-01-02 14:37:35 UTC
Description of problem:
The Openshift on z/VM operator hub shows many operators that do not have s390x compatible images. There is no status to indicate which if any operators will work the cluster. 

For example:
Installing 3scale operator gives:

```Failed to pull image "registry.redhat.io/3scale-amp2/3scale-rhel7-operator:1.10-5": rpc error: code = Unknown desc = no image found in manifest list for architecture s390x, OS linux```

Comment 1 Cheryl A Fillekes 2020-01-03 22:08:41 UTC
Created attachment 1649540 [details]
Red Hat Provided

it's not clear that multi-arch images have been built or tested for OCP on Z, there are 28 operators which promise Red Hat support; so 3scale Operator is just the first of those.  The 54 with Certified support would be next; and we need to find out which repositories/bug reporting we need to use for the IBM certified & provided operators, including the Cloud Paks. https://ibm.box.com/s/hvrrb1v6zs4r88k50rbmd3l79kaejjdt

Comment 2 Cheryl A Fillekes 2020-01-28 23:57:36 UTC
Created attachment 1656131 [details]
Screen Shot of Operator Hub today

Navigating back to OperatorHub to re-test the Template Broker Operator, and there are no operators displayed at all -- not even the five or six that work.

Comment 3 Carvel Baus 2020-06-02 18:42:04 UTC
This is similar to 1810087 which is currently against 4.3. This is not something that can/will be fixed for 4.2 so closing as won't fix. Continue to track on referenced bug.


Note You need to log in before you can comment on or make changes to this bug.