Bug 1827689
| Summary: | OCS 4.3 Installation fails when using OCS 4.4-rc2 registry bundle | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | umanga <uchapaga> | ||||
| Component: | build | Assignee: | Christina Meno <gmeno> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Petr Balogh <pbalogh> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.4 | CC: | bniver, branto, ebenahar, jarrpa, madam, nberry, ocs-bugs, pbalogh, ratamir, rcyriac, sostapov | ||||
| Target Milestone: | --- | Keywords: | AutomationBackLog | ||||
| Target Release: | OCS 4.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 4.4.0-rc6 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1834936 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-06-04 12:54:39 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: | |||||||
| Attachments: |
|
||||||
|
Description
umanga
2020-04-24 14:32:15 UTC
Hi Umanga, Could you please explain what is the use case of choosing `Stable-4.3` while installing 4.4.0-rc2? Thanks Boris for explanation.
> The way we build ocs-olm now, you can install any z-stream version from the latest CSV, you just need to manually select it, i.e. we are shipping all the CSVs for all the released content, including all the z-stream releases.
Do you have any documentation for it? AFAIK in the installation of OCS you are just selecting channel which means stable-4.3 or stable-4.4 for example and it automatically taking the latest available in this channel. That's how auto upgrade roll automatically to latest one version and if you are the customer and installing form scratch new OCS cluster you will get latest version in that channel. If there is the way how to install for example 4.2.0 instead of 4.2.3 I am more than happy to hear how to achieve this.
That is the info I got from Umanga the last time we were talking about it. IIRC, you were supposed to have an option to select it from the web UI. @Umanga: Can you elaborate on how to (manually) select to deploy a release that is not latest for a channel? @umanga, since Petr also reproduced this issue and the newer RC build of OCS 4.4 (i.e 4.4.0-rc3) , we should now consider this BZ as a blocker and try to bring in the fix. AFAIU, Since this involves installation of OCS 4.3 from the 4.4 bundle, we would need to fix it in the same 4.4 release Marking it as a blocker as of now. Let us know if there needs to be a change, we all can have a discussion. When doing this installation, is there an OCS catalog entry from the redhat-operators catalog that has the OCS 4.3 GA CSV? If so, there may be a conflict with having the OCS 4.3 GA CSV being offered from both redhat-operators and ocs-olm-operator. Does that make sense? Can you try disabling the redhat-operators catalog and seeing if the installation succeeds? For now I am adding the must gather logs I've collected on cluster deployed on Thursday with lib bucket provisioner V2. http://rhsqe-repo.lab.eng.blr.redhat.com/cns/ocs-qe-bugs/bz-1827689/ I will try to reproduce with disabled red-hat-operators today and will get to you back with the results. Must gather are in the same path I shared last time in this tar file: http://rhsqe-repo.lab.eng.blr.redhat.com/cns/ocs-qe-bugs/bz-1827689/logs-with-disabled-rh-operator.tar.gz This is now tracking OCP/OLM BZ. acking As decided by the stakeholders, we are falling back to reverting the CRD owning change in ocs-operator. https://github.com/openshift/ocs-operator/pull/518 has been merged to the release branch. 4.3 was verified here: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/7921/parameters/ 4.2 was verified here: https://ocs4-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/qe-deploy-ocs-cluster/7893/parameters/ With build: quay.io/rhceph-dev/ocs-olm-operator:4.4.0-428.ci 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, 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:2393 |