-
Bug
-
Resolution: Done
-
None
-
1
-
False
-
-
False
-
upgrade
-
CLOSED
-
---
-
---
-
-
-
CNV I/U Operators Sprint 228
-
High
-
None
Description of problem:
-----------------------
The upgrading CNV cluster v4.9.7-5(nightly build) to v4.10.7-39(nightly build), has a upgrade path: 4.9.7-5 ->4.10.0 -> 4.10.1 -> 4.10.2 -> 4.10.3 -> 4.10.4 -> 4.10.5 -> 4.10.6 -> 4.10.7-39, which is a longer upgrade path.
Upgrading from CNV v4.9.6(GA) to CNV 4.10.6(GA) had a much lesser hops to upgrade:
4.9.6-> 4.10.4 -> 4.10.5 -> 4.10.6
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
CNV v4.9.7-5
How reproducible:
------------------
Always
Steps to Reproduce:
-------------------
1. Find out the upgrade path of CNV v4.9.7-5 to CNV 4.10.7-39 using CNV explorer tool
Actual results:
---------------
Upgrade path was much longer
4.9.7-5 ->4.10.0 -> 4.10.1 -> 4.10.2 -> 4.10.3 -> 4.10.4 -> 4.10.5 -> 4.10.6 -> 4.10.7-39
Expected results:
-----------------
Much lesser hops to upgrade would be more efficient to upgrade