Bug 2176798 - [IBM Z ] Multi Cluster Orchestrator operator is not available in the Operator Hub
Summary: [IBM Z ] Multi Cluster Orchestrator operator is not available in the Operator...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.13.0
Assignee: umanga
QA Contact: Sravika
URL:
Whiteboard:
Depends On:
Blocks: 2176809 2188327
TreeView+ depends on / blocked
 
Reported: 2023-03-09 10:53 UTC by Sravika
Modified: 2023-08-09 17:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2176809 2188327 (view as bug list)
Environment:
Last Closed: 2023-06-21 15:24:28 UTC
Embargoed:


Attachments (Terms of Use)
operator_hub_mco_not_available (375.79 KB, image/png)
2023-03-09 10:53 UTC, Sravika
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-multicluster-orchestrator pull 155 0 None open Bug 2176798: [release-4.13] add labels for supported arch 2023-03-20 11:32:10 UTC
Red Hat Product Errata RHBA-2023:3742 0 None None None 2023-06-21 15:24:50 UTC

Description Sravika 2023-03-09 10:53:46 UTC
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:

Comment 1 umanga 2023-03-09 11:08:18 UTC
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.

Comment 2 Aaruni Aggarwal 2023-03-09 11:54:16 UTC
Multi-Cluster Orchestrator operator is unavailable in the Operator Hub on IBM Power(ppc64le)as well.

Comment 5 umanga 2023-03-27 11:21:15 UTC
Fixed in v4.13.0-110.

Comment 6 Sravika 2023-03-31 12:10:57 UTC
MCO is now available on IBM Z Operator Hub with ODF v4.13.0-110

Comment 8 Sravika 2023-04-19 15:14:37 UTC
MCO is not available on s390x with the latest GA'd version of ODF 4.12.2-rhodf in OH

Comment 9 Sravika 2023-05-25 08:37:11 UTC
MCO is now available on IBM Z Operator Hub with latest ODF 4.13 builds

Comment 11 errata-xmlrpc 2023-06-21 15:24:28 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 (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


Note You need to log in before you can comment on or make changes to this bug.