Bug 2083726

Summary:	Provide direct upgrade path from 4.8.4 to the next 4.9.z release then to the next 4.10.z release
Product:	Container Native Virtualization (CNV)	Reporter:	Arvin Amirian <aamirian>
Component:	Installation	Assignee:	Simone Tiraboschi <stirabos>
Status:	CLOSED ERRATA	QA Contact:	Natalie Gavrielov <ngavrilo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.8.4	CC:	aamirian, cnv-qe-bugs, dbasunag, kmajcher, stirabos
Target Milestone:	---
Target Release:	4.9.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	hco-bundle-registry-container-v4.9.5-51	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2094344 (view as bug list)		Environment:
Last Closed:	2022-06-28 16:30:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2094344

Description Arvin Amirian 2022-05-10 15:35:50 UTC

Description of problem:

Morgan Stanley's OCP clusters are deployed in a disconnected fashion. Upgrading to the latest version of CNV is painful due to the number of hops required. This results in a ton of images that need to be scanned, approved as well as the complexity of automating the upgrade. The client will be upgrading from OCP 4.8.25 to 4.10.x when the upgrade path becomes available. 

To avoid excessive upgrade hops in a disconnected environment we want to request a direct upgrade path for OCP Virt from 4.8.4 to the next 4.9.x release and the same 4.9.x release to the next 4.10.x release.

Comment 2 Debarati Basu-Nag 2022-05-11 13:38:32 UTC

@stirabos Would this open up direct upgrade path to 4.9.5 from any other 4.8.z builds? e.g. 4.8.5/4.8.6?
This would open up more upgrade lanes for both 4.9.5 and 4.10.3, however, given multiple customers need this path enabled, we would be ok with taking this change. Will add QE ack for this.

Comment 3 Arvin Amirian 2022-05-11 14:34:05 UTC

This will be an upgrade from 4.8.4 ->  4.9.5 -> 4.10.3

Comment 7 Debarati Basu-Nag 2022-06-08 15:36:22 UTC

Verified ability to upgrade 4.8.4->4.9.5
=================================

Last login: Tue Jun  7 23:35:00 2022 from 10.22.8.227
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$ kubectl get csv -n openshift-cnv
NAME                                      DISPLAY                    VERSION   REPLACES                                  PHASE
kubevirt-hyperconverged-operator.v4.8.4   OpenShift Virtualization   4.8.4     kubevirt-hyperconverged-operator.v4.8.3   Succeeded
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$ kubectl get hco kubevirt-hyperconverged -n openshift-cnv -o json| jq ".status.versions"
[
  {
    "name": "operator",
    "version": "v4.8.4"
  }
]
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$  kubectl get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.36    True        False         11h     Cluster version is 4.9.36
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$  kubectl get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.36    True        False         14h     Cluster version is 4.9.36
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$ kubectl get hco kubevirt-hyperconverged -n openshift-cnv -o json| jq ".status.versions"
[
  {
    "name": "operator",
    "version": "v4.9.5"
  }
]
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$ kubectl get csv -n openshift-cnv
NAME                                      DISPLAY                    VERSION   REPLACES                                  PHASE
kubevirt-hyperconverged-operator.v4.9.5   OpenShift Virtualization   4.9.5     kubevirt-hyperconverged-operator.v4.8.4   Succeeded
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$ kubectl get hco kubevirt-hyperconverged -n openshift-cnv -o json| jq ".status.conditions"
[
  {
    "lastTransitionTime": "2022-06-07T22:39:05Z",
    "message": "Reconcile completed successfully",
    "observedGeneration": 7,
    "reason": "ReconcileCompleted",
    "status": "True",
    "type": "ReconcileComplete"
  },
  {
    "lastTransitionTime": "2022-06-08T13:37:26Z",
    "message": "Reconcile completed successfully",
    "observedGeneration": 7,
    "reason": "ReconcileCompleted",
    "status": "True",
    "type": "Available"
  },
  {
    "lastTransitionTime": "2022-06-08T13:37:26Z",
    "message": "Reconcile completed successfully",
    "observedGeneration": 7,
    "reason": "ReconcileCompleted",
    "status": "False",
    "type": "Progressing"
  },
  {
    "lastTransitionTime": "2022-06-08T13:37:26Z",
    "message": "Reconcile completed successfully",
    "observedGeneration": 7,
    "reason": "ReconcileCompleted",
    "status": "False",
    "type": "Degraded"
  },
  {
    "lastTransitionTime": "2022-06-08T13:37:26Z",
    "message": "Reconcile completed successfully",
    "observedGeneration": 7,
    "reason": "ReconcileCompleted",
    "status": "True",
    "type": "Upgradeable"
  }
]
[cnv-qe-jenkins@c01-dbn-484-fjw2p-executor ~]$

Comment 13 errata-xmlrpc 2022-06-28 16:30:39 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Virtualization 4.9.5 Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:5389