Description of problem: Upgrade from 4.12.4 currently goes through 4.13.0. So any customer with this fg enabled would have this undone if they upgrade to 4.13.z before 4.13.2 gets released. So we need a direct upgrade path 4.12.4->4.13.2 and possibly can't have a gap between the two without a release note. Version-Release number of selected component (if applicable): CNV 4.12.4 and 4.13.2 How reproducible: NA Steps to Reproduce: 1. NA 2. 3. Actual results: Expected results: Additional info:
Verified with 4.13.2-38: [cloud-user@ocp-ipi-executor-xl ~]$ oc get hco kubevirt-hyperconverged -n openshift-cnv -o json | jq ".status.versions" [ { "name": "operator", "version": "4.13.2" } ] [cloud-user@ocp-ipi-executor-xl ~]$ oc get csv -n openshift-cnv NAME DISPLAY VERSION REPLACES PHASE kubevirt-hyperconverged-operator.v4.13.2 OpenShift Virtualization 4.13.2 kubevirt-hyperconverged-operator.v4.12.4 Succeeded openshift-pipelines-operator-rh.v1.11.0 Red Hat OpenShift Pipelines 1.11.0 Succeeded [cloud-user@ocp-ipi-executor-xl ~]$
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.13.2 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-2023:4028