Bug 2079721

Summary: Openshift data foundation version does not upgrade from 4.9 to 4.10
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Ishwarya Munesh <ishwaryax.munesh>
Component: odf-operatorAssignee: Nitin Goyal <nigoyal>
Status: CLOSED NOTABUG QA Contact: Martin Bukatovic <mbukatov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.10CC: brault, etamir, jrivera, muagarwa, nigoyal, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-28 12:00:23 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 Flags
channel 4.10 selected
none
4.10 version not updated
none
oc get csv output none

Description Ishwarya Munesh 2022-04-28 07:07:48 UTC
Created attachment 1875581 [details]
channel 4.10 selected

Description of problem (please be detailed as possible and provide log
snippests):

ODF version does not upgrade from 4.9 to 4.10 after selecting the 'stable-4.10' channel under Subscription tab.


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Drive detach test is expected to be tested on 4.10 version which is blocked due to this upgrade issue.

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)?
4

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.1. Upgraded OCP version from 4.9.22 to 4.10.4
2. To upgrade ODF from 4.9 to 4.10, in cluster console UI,
Installed Operators -> ODF-> Subscription -> update channel, selected 'stable-4.10' option -> Save



Actual results:
There is no upgrade process or any progress seen after selecting the 4.10 channel. Version of ODF also not updated to 4.10.

Expected results:
Upgrade should happen for ODF after selecting the channel under Subscription.

Additional info:
oc get csv shows Openshift container storage operator versions 4.9.5 & 4.9.6 in Installing and Pending states respectively.
Attached screenshots.

Comment 1 Ishwarya Munesh 2022-04-28 07:08:51 UTC
Created attachment 1875582 [details]
4.10 version not updated

Comment 2 Ishwarya Munesh 2022-04-28 07:09:53 UTC
Created attachment 1875583 [details]
oc get csv output

Comment 3 Nitin Goyal 2022-04-28 08:45:40 UTC
Hello Ishwarya, I see that It is still installing ocs-operator 4.9.5 and ocs-operator 4.9.6 is in the pending state from your CSV output. I think we should wait for these to be installed successfully and then only we should upgrade. Can I get a must-gather for this cluster?

Is this a production environment?

Comment 5 Ishwarya Munesh 2022-04-28 08:52:58 UTC
Hi Nitin, the ocs-operator 4.9.5 to 4.9.6 is still in same Installing and Pending state for more than 15hours. This is not a production environment. Openshift cluster is installed on a bare-metal using UPI method.
Must gather logs are placed in the dropbox location - https://www.dropbox.com/home/Must-Gather
since BZ doesn't allow huge file upload.

Comment 6 Nitin Goyal 2022-04-28 09:19:07 UTC
I looked at the given OCP must gather and found below failure in the CSV. It is waiting for ocs-operator which is not ready. Can I get an ocs/odf must gather to look at the operators status?

 message: 'installing: waiting for deployment ocs-operator to become ready: deployment
      "ocs-operator" not available: Deployment does not have minimum availability.'

Comment 7 Nitin Goyal 2022-04-28 11:29:22 UTC
I helped Ishwarya over the coreos slack, Her operator was down as it was not able to pull the image. Deleting the pod worked well and her cluster is also upgraded to 4.10.



ocs-operator-76945b4575-jn8vx                                     0/1     ImagePullBackOff   1              5d11h


Ishwarya I would like to close the BZ. I will wait for some time before closing it. Pls, let me know if you have any objections or further help required with this?

Comment 8 Ishwarya Munesh 2022-04-28 11:49:45 UTC
Hi Nitin, ODF got upgraded to 4.10 now and we can now see the version update in the console as well. Thanks for your support!. This ticket can be closed.

Comment 9 Nitin Goyal 2022-04-28 12:00:23 UTC
Thanks for the confirmation Ishwarya, also thanks for providing all the required details to debug the issue.