Bug 2064553 - UI should prefer to use the virtio-win configmap than v2v-vmware configmap for windows creation
Summary: UI should prefer to use the virtio-win configmap than v2v-vmware configmap fo...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Oren Cohen
QA Contact: Guohua Ouyang
Depends On:
Blocks: 2078385
TreeView+ depends on / blocked
Reported: 2022-03-16 07:25 UTC by Guohua Ouyang
Modified: 2022-08-10 10:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:54:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
v2v-vmware cm (1.95 KB, text/plain)
2022-03-16 07:26 UTC, Guohua Ouyang
no flags Details
virtio-win cm (1.10 KB, text/plain)
2022-03-16 07:28 UTC, Guohua Ouyang
no flags Details

System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 1824 0 None open WIP: remove leftovers during upgrades 2022-03-21 13:16:14 UTC
Github openshift console pull 11207 0 None open Remove reference to deprecated `v2v-vmware` ConfigMap 2022-03-21 13:16:19 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:54:54 UTC

Description Guohua Ouyang 2022-03-16 07:25:28 UTC
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):

How reproducible:

Steps to Reproduce:
1. upgrade cluster from 4.8 to 4.10
2. create a windows VM

Actual results:
Windows guest tool disk is using image from v2v-vmware

Expected results:
Windows guest tool disk is using image from virtio-win

Additional info:

Comment 1 Guohua Ouyang 2022-03-16 07:26:38 UTC
Created attachment 1866151 [details]
v2v-vmware cm

Comment 2 Guohua Ouyang 2022-03-16 07:28:03 UTC
Created attachment 1866152 [details]
virtio-win cm

Comment 4 Oren Cohen 2022-03-21 13:00:56 UTC
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)

Comment 5 Oren Cohen 2022-03-23 14:58:52 UTC
Guohua, do we want to backport the fix also for 4.10.z?

Comment 8 Guohua Ouyang 2022-04-25 07:40:32 UTC
(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.

Comment 9 Oren Cohen 2022-04-28 08:32:47 UTC
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?

Comment 10 Guohua Ouyang 2022-04-28 10:58:21 UTC
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.

Comment 12 errata-xmlrpc 2022-08-10 10:54:28 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 (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.


Note You need to log in before you can comment on or make changes to this bug.