+++ This bug was initially created as a clone of Bug #2176798 +++ 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: --- Additional comment from umanga on 2023-03-09 16:38:18 IST --- 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. --- Additional comment from Aaruni Aggarwal on 2023-03-09 17:24:16 IST --- Multi-Cluster Orchestrator operator is unavailable in the Operator Hub on IBM Power(ppc64le)as well. --- Additional comment from RHEL Program Management on 2023-03-25 12:58:34 IST --- This BZ is being approved for ODF 4.13.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'odf‑4.13.0 --- Additional comment from RHEL Program Management on 2023-03-25 12:58:34 IST --- Since this bug has been approved for ODF 4.13.0 release, through release flag 'odf-4.13.0+', the Target Release is being set to 'ODF 4.13.0 --- Additional comment from umanga on 2023-03-27 16:51:15 IST --- Fixed in v4.13.0-110. --- Additional comment from Sravika on 2023-03-31 17:40:57 IST --- MCO is now available on IBM Z Operator Hub with ODF v4.13.0-110 --- Additional comment from errata-xmlrpc on 2023-04-04 18:29:45 IST --- This bug has been added to advisory RHBA-2023:108078 by Boris Ranto (branto) --- Additional comment from Sravika on 2023-04-19 20:44:37 IST --- MCO is not available on s390x with the latest GA'd version of ODF 4.12.2-rhodf in OH
With 4.12.3-11 (4.12.3rhodf), MCO is available in the Operator hub on IBM Z
Moving the bug to verification based on the comment above.
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 (Moderate: Red Hat OpenShift Data Foundation 4.12.3 Security 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/RHSA-2023:3265