Bug 2110815 - Upgrade to ODF 4.10.5 from 4.9.9 did not start
Summary: Upgrade to ODF 4.10.5 from 4.9.9 did not start
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.10
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Nitin Goyal
QA Contact: Martin Bukatovic
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-26 00:58 UTC by James Biao
Modified: 2023-08-09 17:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-03 08:13:52 UTC
Embargoed:


Attachments (Terms of Use)

Description James Biao 2022-07-26 00:58:12 UTC
Description of problem (please be detailed as possible and provide log
snippests):

In the subscription we see
    Message:                constraints not satisfiable: subscription ocs-operator exists, no operators found in channel stable-4.9 of package ocs-operator in the catalog referenced by subscription ocs-operator
    Reason:                 ConstraintsNotSatisfiable
    Status:                 True
    Type:                   ResolutionFailed

Version of all relevant components (if applicable):
ODF 4.9.9 
OCP 4.10.22
Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Upgrade didn't start

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


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


Can this issue reproducible?

Once in customer environment
Can this issue reproduce from the UI?


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


Steps to Reproduce:
1. Upgrade from ODF 4.9.9 to 4.10
2.
3.


Actual results:
Upgrade did not start 

Expected results:

Upgrade start
Additional info:

Comment 4 Mudit Agarwal 2022-07-26 05:55:22 UTC
Nitin, please take a look


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