Description of problem:
On a cluster that has both v2v-vmware and virtio-win configmaps to provide virtio-win-image for windows VM creation, UI should prefer to use virtio-win than v2v-vmware configmap
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. upgrade cluster from 4.8 to 4.10
2. create a windows VM
Windows guest tool disk is using image from v2v-vmware
Windows guest tool disk is using image from virtio-win
Created attachment 1866151 [details]
Created attachment 1866152 [details]
This BZ is handled both in UI and in HCO.
In UI, the reference for the deprecated configmap "v2v-vmware" is being removed:
In HCO, we'll remove the deprecated v2v-vmware ConfigMap on upgrade to the next version using a new mechanism for leftovers removal using a json file:
https://github.com/kubevirt/hyperconverged-cluster-operator/pull/1824 (currently WIP)
Guohua, do we want to backport the fix also for 4.10.z?
(In reply to Oren Cohen from comment #5)
> Guohua, do we want to backport the fix also for 4.10.z?
I think we should backport the fix to 4.10.z.
Hi @gouyang ,
Could you please move this BZ (targeting 4.11) to verified, so the backport to 4.10 (https://bugzilla.redhat.com/show_bug.cgi?id=2078385, https://github.com/openshift/console/pull/11387) could be merged?
On a cluster which hava CNV upgrade from 4.9.z to 4.10.z, and then could reproduce the bug on OCP upstream 4.10 and verified this on OCP upstream 4.11.
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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.