Bug 2013197 - Unable to change the upgrade strategy from manual to automatic
Summary: Unable to change the upgrade strategy from manual to automatic
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Nishanth Thomas
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-12 11:02 UTC by Bipin Kunal
Modified: 2023-08-09 16:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-13 06:25:38 UTC
Embargoed:


Attachments (Terms of Use)
Upgrade Strategy change error (195.15 KB, image/png)
2021-10-12 11:02 UTC, Bipin Kunal
no flags Details

Description Bipin Kunal 2021-10-12 11:02:30 UTC
Created attachment 1832181 [details]
Upgrade Strategy change error

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

Changing the update approval strategy from automatic to manual gives an error.

=========================
Danger alert:An error occurred
r: Operation cannot be fulfilled on subscriptions.operators.coreos.com "odf-operator": the object has been modified; please apply your changes to the latest version and try again
=========================


Version of all relevant components (if applicable):
OCP : 4.9.0-0.nightly-2021-10-11-151207
ODF :
      Installed :  quay.io/rhceph-dev/ocs-registry:4.9.0-183.ci
      trying to upgrading to : quay.io/rhceph-dev/ocs-registry:4.9.1-186.ci



Additional Info:

  I am in the middle of the upgrade. I initially installed ODF-4.9.0 and trying to upgrade to 4.9.1 with an internal build. I have recreated the catalogsource with 4.9.1 to force the upgrade of ODF operator. Unfortunately, the upgrade doesn't trigger. But the upgrade is an altogether different story and the issue is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=2008752. 

  After changing the catalogsource for upgrade I was trying to change the upgrade strategy( was just doing something random while the upgrade was not getting triggered) and then I ended up with the error mentioned above. This doesn't allow me to change the upgrade strategy.

  In the update channel, I do see 4.9.1 but the upgrade is not triggering and it is not allowing me to change the upgrade strategy


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