Bug 2127029 - Unable to upgrade from ODF v4.10.z to ODF v4.11.z
Summary: Unable to upgrade from ODF v4.10.z to ODF v4.11.z
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-managed-service
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Boris Ranto
QA Contact: suchita
URL:
Whiteboard:
Depends On:
Blocks: 2126791
TreeView+ depends on / blocked
 
Reported: 2022-09-15 06:50 UTC by Dhruv Bindra
Modified: 2024-02-09 06:30 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2126791
Environment:
Last Closed: 2024-02-09 06:30:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhruv Bindra 2022-09-15 06:50:18 UTC
+++ This bug was initially created as a clone of Bug #2126791 +++

Description of problem:
We are unable to upgrade from ODF v4.10.z to ODF v4.11.z due to a known issue in ceph. The upgrade is intentionally blocked by ODF because it impacts the customers that are using RGW but in managed service the customers do not use RGW  so as a workaround ODF build team will provide the custom build of ODF that will have the correct olm.skipRange(this range should allow upgrade from v4.10.z to v4.11.z) and all the serviceAccounts should have reference to a pullSecret as the images are not public. This workaround should be used until a fix comes in a z-stream of ODF v4.11 and the ocs-osd-deployer will update the subscription with the correct channel after the fix is introduced in a z-stream.


Version-Release number of selected component (if applicable):


How reproducible:
Always reproducible

Steps to Reproduce:
https://docs.google.com/document/d/1gm-msSAEWsk-bM8Dvdd_IDHUJuf8RjEKoOS1k7q26cY/edit#bookmark=id.rnqpvqhp6m2z

Actual results:
Unable to upgrade from ODF v4.10.z to v4.11.z

Expected results:
Able to upgrade from ODF v4.10.z to v4.11.z

Additional info:
Link to the conversation: https://chat.google.com/room/AAAASHA9vWs/wwCAEHNHQjQ

Comment 2 Boris Ranto 2022-09-15 08:13:10 UTC
We need to know what ODF 4.11.z version you are interested in? We have already shipped 4.11.1 so I expect you will want to use at least that version, right? (i.e. you are not interested in 4.11.0 now?)

Comment 3 Dhruv Bindra 2022-09-15 08:39:12 UTC
We will need a custom build for ODF v4.11.1(we are skipping ODF v4.11.0 as we need a few fixes in ODF v4.11.1)

Comment 4 Boris Ranto 2022-09-15 17:52:35 UTC
The build is now available:

quay.io/rhceph-dev/odf4-odf-compose-operator-bundle-index:4.11.1-10

Comment 12 suchita 2023-09-12 13:08:18 UTC
This has been tested while qualification of v2.1.0 release testing.

while upgrade oc v2.0.13 to v2.1.0,OCS operator	4.10.9 upgraded successfully to ocs-operator full version 4.11.10

Acceptance test passed on upgraded ODF clusters.
 http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/ikave-mpl60-pr/ikave-mpl60-pr_20230829T075130/multicluster/logs/test_report_1693379018.html

Based on this observation, marking this BZ as verified.


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