Description of problem:MachineType in KV CR is still pc-q35-rhel9.0.0 and not updated to pc-q35-rhel9.2.0 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.$ oc get kubevirt kubevirt-kubevirt-hyperconverged -n openshift-cnv -o yaml | grep machineType* 2. 3. Actual results: machineType: pc-q35-rhel9.0.0 Expected results: machineType: pc-q35-rhel9.2.0 Additional info:
I think we could have released 4.13.0 with no support for 9.2 the machine type. Why was this bug considered a blocker? It does not matter too much now, just interesting.
Many test cases would fail at Tier2 end, if this is not fixed. We should keep Templates machine Type in sync with KV CR default value.
~]$ oc get kubevirt kubevirt-kubevirt-hyperconverged -n openshift-cnv -o yaml | grep machineType machineType: pc-q35-rhel9.2.0 KV CR is updated to above value. As per build: v4.13.0.rhel9-1971
Kedar is correct. I think where we went wrong here is this should have been marked as a TestBlocker.
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 (Moderate: OpenShift Virtualization 4.13.0 Images security, bug fix, and enhancement update), 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/RHSA-2023:3205