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

Bug 1855316

Summary:	ppc64le & s390x Operators filtered in Operator Hub for 4.4
Product:	OpenShift Container Platform	Reporter:	Andy McCrae <amccrae>
Component:	Logging	Assignee:	Andy McCrae <amccrae>
Status:	CLOSED ERRATA	QA Contact:	Barry Donahue <bdonahue>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	agreene, anli, aos-bugs, carangog, cshepher, dorzel, dslavens, ecordell, jiazha, krizza, lakshmi.ravichandran1, periklis, pfruth, tdale
Target Milestone:	---	Keywords:	UpcomingSprint
Target Release:	4.4.z
Hardware:	Unspecified
OS:	Linux
Whiteboard:	multi-arch, logging-core, logging-exploration
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Multi-Arch operators were missing the operatorframework.io/arch.$ARCH=supported flag in the cluster service version metadata. Consequence: Supported operators do not show up in Operator Hub for non-x86_64 architectures. Fix: Add operatorframework.io/arch.$ARCH=supported metadata for ppc64le and s390x for the supported operators (cluster-logging-operator, elasticsearch-operator, cluster-nfd-operator). Result: The Multi-Arch supported operators (cluster-logging-operator, elasticsearch-operator, cluster-nfd-operator) appear in the Operator Hub in ppc64le/s390x deployments.	Story Points:	---
Clone Of:	1850546	Environment:
Last Closed:	2020-11-11 01:08:01 UTC	Type:	---
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:	1855312
Bug Blocks:	1855322

Description Andy McCrae 2020-07-09 14:31:07 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 3 Jeff Cantrill 2020-07-15 21:01:05 UTC

@Andy assigning directly to you do do the backport

Comment 4 Andy McCrae 2020-07-16 14:34:26 UTC

*** Bug 1857235 has been marked as a duplicate of this bug. ***

Comment 7 Anping Li 2020-10-22 01:48:29 UTC

The  s390x & ppc64le had been added to logging operators

$ oc get csv elasticsearch-operator.4.4.0-202010081339.p0 -o yaml |grep -B 4 s390
    olm.api.e43efcaa45c9f8d0: provided
    olm.copiedFrom: openshift-operators-redhat
    operatorframework.io/arch.amd64: supported
    operatorframework.io/arch.ppc64le: supported
    operatorframework.io/arch.s390x: supported
$ oc get csv clusterlogging.4.4.0-202010081339.p0 -o yaml  |grep -B 4 s390
    olm.api.398cc1f7861443fe: provided
    olm.api.b997d85fc603bbcf: provided
    operatorframework.io/arch.amd64: supported
    operatorframework.io/arch.ppc64le: supported
    operatorframework.io/arch.s390x: supported

Comment 8 Anping Li 2020-10-22 03:08:14 UTC

The  s390x & ppc64le had been added to nfd.4.4.0-202010212202.p0
$ oc get csv nfd.4.4.0-202010212202.p0 -o yaml |grep 390 -A 2 -B 2
    operatorframework.io/arch.amd64: supported
    operatorframework.io/arch.ppc64le: supported
    operatorframework.io/arch.s390x: supported
  name: nfd.4.4.0-202010212202.p0
  namespace: openshift-logging

Comment 9 Barry Donahue 2020-10-22 12:52:41 UTC

Doug, do you know how to test this BZ?

Comment 10 Douglas Slavens 2020-10-22 18:08:31 UTC

Here are the results of my testing so far:

http://pastebin.test.redhat.com/912434

I am not seeing the available operator list in either the webconsole or the shell. I am testing on a 4.6 cluster because I have it currently available, but it seems like the list of operators would be visible to any OCP 4.4/4.5/4.6 cluster correct?

Comment 11 Douglas Slavens 2020-10-22 18:17:22 UTC

Additional update:

When Carvel executed the command, he did see the nfd operator so we were wondering why the other two do not appear in the list:

[cbaus@rock-kvmlp-3 ocp4-workdir]$ oc version
Client Version: 4.5.6
Server Version: 4.6.1
Kubernetes Version: v1.19.0+d59ce34


[cbaus@rock-kvmlp-3 ocp4-workdir]$ oc get packagemanifests -l operatorframework.io/arch.s390x=supported
NAME                     CATALOG               AGE
openshift-nfd-operator   Community Operators   176m
[cbaus@rock-kvmlp-3 ocp4-workdir]$

Comment 12 Douglas Slavens 2020-10-23 15:27:12 UTC

This is verified for the target release 4.4.

Comment 15 errata-xmlrpc 2020-11-11 01:08:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.4.30 extras update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4323