-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
0.42
-
False
-
False
-
NoActiveCustomerTickets
-
CLOSED
-
Undefined
-
CNV I/U Operators Sprint 202
-
Medium
-
No
Description of problem:
The current CNV upgrade path is far too restrictive. As you can see from the table below, If someone wanted to upgrade from 2.5.0 to 2.6.2 they would need to do 7 upgrades. This is quite painful for customers especially in a disconnected environment. A Y to Y+1 should be available.
version replaces skiprange
------- --------------------------------------- --------------
2.1.0
2.2.0 kubevirt-hyperconverged-operator.v2.1.0
2.3.0 kubevirt-hyperconverged-operator.v2.2.0
2.4.0 kubevirt-hyperconverged-operator.v2.3.0
2.4.1 kubevirt-hyperconverged-operator.v2.4.0
2.4.2 kubevirt-hyperconverged-operator.v2.4.1
2.4.3 kubevirt-hyperconverged-operator.v2.4.2
2.4.4 kubevirt-hyperconverged-operator.v2.4.3
2.5.0 kubevirt-hyperconverged-operator.v2.4.3
2.5.1 kubevirt-hyperconverged-operator.v2.5.0
2.5.2 kubevirt-hyperconverged-operator.v2.5.1 >=2.4.4 <2.5.0
2.4.5 kubevirt-hyperconverged-operator.v2.4.4
2.5.3 kubevirt-hyperconverged-operator.v2.5.2
2.5.4 kubevirt-hyperconverged-operator.v2.5.3 >=2.4.6 <2.5.0
2.6.0 kubevirt-hyperconverged-operator.v2.5.4 >=2.5.4 <2.6.0
2.6.1 kubevirt-hyperconverged-operator.v2.6.0
2.6.2 kubevirt-hyperconverged-operator.v2.6.1
Version-Release number of selected component (if applicable):
All
How reproducible:
Every time
Steps to Reproduce:
1. Install OpenShift 2.5.0
2. Attempt to upgrade to 2.6.2.
Actual results:
You will need to do 7 upgrades to get to 2.6.2
Expected results:
I should be able to upgrade from 2.5.0 to 2.6.2 with a maximum of 2 upgrades
Additional info:
- external trackers