Bug 2177315
| Summary: | [4.8.18] Operatorhub doesn't list latest 4.8.18 build | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | shylesh <shmohan> |
| Component: | build | Assignee: | Tamil <tmuthami> |
| Status: | CLOSED NOTABUG | QA Contact: | Petr Balogh <pbalogh> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | branto, muagarwa, ocs-bugs, odf-bz-bot, oviner, pbalogh |
| Target Milestone: | --- | Keywords: | Automation |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-03-13 07:12:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Logs are located at http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/j-273vuf1cs36-t4a/j-273vuf1cs36-t4a_20230310T145136/ As such, this is not a product bug. We used OCP 4.9 index image instead of OCP 4.8 index image by default and that made the build unavailable, closing this bz as NOTABUG. The defaults are now fixed. |
Description of problem (please be detailed as possible and provide log snippests): After deploying OCP 4.8 trying to install openshift container storage operator 4.8 from operatorhub doesn't list 4.8 at all. Version of all relevant components (if applicable): 4.8.18 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes, not able to install OCS Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Deploy OCP 4.8 cluster 2. patch catalogsource and create 4.8.18 catalogsource ============================================== # oc patch operatorhub.config.openshift.io/cluster -p='{"spec":{"sources":[{"disabled":true,"name":"redhat-operators"}]}}' --type=merge 2023-03-10 07:25:58 15:25:56 - MainThread - ocs_ci.deployment.deployment - INFO - Adding CatalogSource 2023-03-10 07:25:58 15:25:56 - MainThread - ocs_ci.utility.templating - INFO - apiVersion: operators.coreos.com/v1alpha1 2023-03-10 07:25:58 kind: CatalogSource 2023-03-10 07:25:58 metadata: 2023-03-10 07:25:58 labels: 2023-03-10 07:25:58 ocs-operator-internal: 'true' 2023-03-10 07:25:58 name: redhat-operators 2023-03-10 07:25:58 namespace: openshift-marketplace 2023-03-10 07:25:58 spec: 2023-03-10 07:25:58 displayName: Openshift Container Storage 2023-03-10 07:25:58 icon: 2023-03-10 07:25:58 base64data: '' 2023-03-10 07:25:58 mediatype: '' 2023-03-10 07:25:58 image: quay.io/rhceph-dev/ocs-registry:4.8.18-2 2023-03-10 07:25:58 priority: 100 2023-03-10 07:25:58 publisher: Red Hat 2023-03-10 07:25:58 sourceType: grpc 2023-03-10 07:25:58 updateStrategy: 2023-03-10 07:25:58 registryPoll: 2023-03-10 07:25:58 interval: 15m 2023-03-10 07:25:58 2023-03-10 07:25:58 15:25:56 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc apply -f /tmp/catalog_source_manifestf2p79qc7 2023-03-10 07:25:58 15:25:58 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n openshift-marketplace get CatalogSource redhat-operators -n openshift-marketplace -o yaml 2.From UI console try to install 'openshift container storage' Actual results: 4.8.18 will not be listed at all Expected results: 4.8.18 should be listed Additional info: However, if we default the catalogsource then we could see 4.8.17 which is the Live version. setup available for inspection: https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster-prod/7153 Currently we have reverted the catalogsource to default.