Bug 2143455 - OCS upgrade from 4.6 to 4.8 results in ocs-operator and noobaa-endpoint pods going down
Summary: OCS upgrade from 4.6 to 4.8 results in ocs-operator and noobaa-endpoint pods ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-17 01:21 UTC by bmcmurra
Modified: 2023-08-09 16:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-06 16:22:36 UTC
Embargoed:

Attachments (Terms of Use)

Comment 2 Elad 2022-11-20 08:47:30 UTC 
Hi, 

It looks like the customer tried upgrading directly from 4.6 to 4.8:

NAME                   DISPLAY                       VERSION   REPLACES               PHASE
ocs-operator.v4.8.15   OpenShift Container Storage   4.8.15    ocs-operator.v4.6.15   Installing


Such an upgrade path is not supported. 

This is probably a dup of bug 2032690
Note You need to log in before you can comment on or make changes to this bug.