Bug 1787358

Summary: Operator Hub shows many operators that are not built for s390
Product: OpenShift Container Platform Reporter: Tom Dale <tdale>
Component: Multi-ArchAssignee: Andy McCrae <amccrae>
Status: CLOSED WONTFIX QA Contact: Barry Donahue <bdonahue>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.2.zCC: alklein, amccrae, cbaus, cfillekes, chanphil, christian.lapolt, dbenoit, dgilmore, dorzel, hannsj_uhl, Holger.Wolf, krmoser, nbziouec, rcgingra, tdale
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: 2020-06-02 18:42:04 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:    
Bug Blocks: 1765215    
Attachments:
Description Flags
Red Hat Provided
none
Screen Shot of Operator Hub today none

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.