+++ 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.
As Kevin metioned above: This bug is not explicitly on OLM, but on a set of operators depending on OLM. Seems like the cluster-logging doesn't support the s390x&ppc64le. mac:~ jianzhang$ oc describe packagemanifest cluster-logging | grep -F "operatorframework.io/arch." operatorframework.io/arch.amd64=supported ... Default Channel: 4.5 Package Name: cluster-logging mac:~ jianzhang$ oc describe packagemanifest elasticsearch-operator | grep -F "operatorframework.io/arch." operatorframework.io/arch.amd64=supported operatorframework.io/arch.ppc64le=supported operatorframework.io/arch.s390x=supported
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.5.5 bug fix 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:3188