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

Hello, I have a customer who's ODF upgrade isn't commencing even though the ODF subscription has been changed to 4.13:

[bmcmurra@supportshell-1 03897473]$ omc get sub
NAME PACKAGE SOURCE CHANNEL
mcg-operator-stable-4.12-redhat-operators-openshift-marketplace mcg-operator redhat-operators stable-4.12
ocs-operator-stable-4.12-redhat-operators-openshift-marketplace ocs-operator redhat-operators stable-4.12
odf-csi-addons-operator-stable-4.12-redhat-operators-openshift-marketplace odf-csi-addons-operator redhat-operators stable-4.12
odf-operator odf-operator redhat-operators stable-4.13

[bmcmurra@supportshell-1 03897473]$ odfcsv
NAME DISPLAY VERSION REPLACES PHASE
mcg-operator.v4.12.14-rhodf NooBaa Operator 4.12.14-rhodf mcg-operator.v4.12.12-rhodf Succeeded
ocs-operator.v4.12.14-rhodf OpenShift Container Storage 4.12.14-rhodf ocs-operator.v4.12.12-rhodf Succeeded
odf-csi-addons-operator.v4.12.14-rhodf CSI Addons 4.12.14-rhodf odf-csi-addons-operator.v4.12.12-rhodf Succeeded
odf-operator.v4.12.14-rhodf OpenShift Data Foundation 4.12.14-rhodf odf-operator.v4.12.12-rhodf Succeeded
openshift-gitops-operator.v1.13.1 Red Hat OpenShift GitOps 1.13.1 openshift-gitops-operator.v1.12.2 Succeeded
vault-secrets-operator.v0.7.1 Vault Secrets Operator 0.7.1 vault-secrets-operator.v0.7.0 Succeeded
[supportshell-1.sush-001.prod.us-west-2.aws.redhat.com] [21:37:39+0000]
[bmcmurra@supportshell-1 03897473]$ ls
0010-must-gather.tar.gz 0020-subs.txt 0030-odf_update.png 0040-must-gather.tar.gz 0050-must-gather.local.3373980112832587952.tar.gz

• Normally I would just use [1] to recover from this, but using [1] is a workaround to what I consider to be a bug. ODF upgrades shouldn't require manual intervention like deletion of subs and csv's.

• [1] does not work for this customer because they need an automated way of initiating ODF upgrades with ArgoCD, but when they simply edit the subscription, they reliably see the above output, and are foreced to manually delete subs, csvs and other CRs as described in [1]

[1] https://access.redhat.com/solutions/7020921

Version of all relevant components (if applicable):
ODF 4.13

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes

Is there any workaround available to the best of your knowledge?
Unknown

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
3

Can this issue reproducible?
Yes, in the customers environment at least. I've still yet to test this in the lab.

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
N/A

Steps to Reproduce:
1.
2.
3.

Actual results:
ODF upgrades require manual intervention like deletion of subs and csv's.

Expected results:
ODF upgrades do not require manual intervention like deletion of subs and csv's.

Additional info:
I have an OCP and ODF must-gather in supportshell taken from the OCP cluster while it's in this stalled upgrade state:

[bmcmurra@supportshell-1 03897473]$ ll
total 116
drwxrwxrwx+ 3 yank yank 59 Aug 8 21:57 0010-must-gather.tar.gz
rw-rw-rw+ 1 yank yank 12016 Aug 14 14:56 0020-subs.txt
rw-rw-rw+ 1 yank yank 105115 Aug 16 18:09 0030-odf_update.png
drwxrwxrwx+ 3 yank yank 59 Sep 25 17:03 0040-must-gather.tar.gz
drwxrwxrwx+ 3 yank yank 59 Sep 26 08:43 0050-must-gather.local.3373980112832587952.tar.gz