Created attachment 1949275 [details] operator_hub_mco_not_available Description of problem (please be detailed as possible and provide log snippests): Multi Cluster Orchestrator operator is not available in the Operator Hub when openshift is installed on IBM Z Version of all relevant components (if applicable): OCP- 4.13.0-ec.2 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Deploy mco using operator-sdk Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Yes Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Deploy ocp 4.13.0-ec.2 on s390x 2. 3. Actual results: Multi Cluster Orchestrator operator is not available in the Operator Hub Expected results: Multi Cluster Orchestrator operator should be available in the Operator Hub Additional info:
Few labels are missing from CSV: ``` labels: operatorframework.io/arch.amd64: supported operatorframework.io/arch.ppc64le: supported operatorframework.io/arch.s390x: supported ``` Due to these missing labels, Operator Hub UI does not list DR operators as avaliable for these arch. All operators are already built for these archs and works. We should add the labels to ensure it's available in UI too.
Multi-Cluster Orchestrator operator is unavailable in the Operator Hub on IBM Power(ppc64le)as well.
Fixed in v4.13.0-110.
MCO is now available on IBM Z Operator Hub with ODF v4.13.0-110
MCO is not available on s390x with the latest GA'd version of ODF 4.12.2-rhodf in OH
MCO is now available on IBM Z Operator Hub with latest ODF 4.13 builds
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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and 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-2023:3742