Bug 1875797 - [v2v][UI] remove vmware-to-kubevirt-os warning from vmWare import wizard
Summary: [v2v][UI] remove vmware-to-kubevirt-os warning from vmWare import wizard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.6.0
Assignee: Filip Krepinsky
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-04 11:56 UTC by Filip Krepinsky
Modified: 2020-10-27 16:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:37:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6532 0 None closed Bug 1875797: remove vmware-to-kubevirt-os warning from vmWare import wizard 2020-10-14 07:53:58 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:38:06 UTC

Description Filip Krepinsky 2020-09-04 11:56:56 UTC 
Description of problem:
this warning is non essential and should not be highlighted by the wizard when vmware-to-kubevirt-os config map is missing
Comment 1 Yaacov Zamir 2020-09-09 11:25:43 UTC 

*** This bug has been marked as a duplicate of bug 1845408 ***
Comment 2 Ilanit Stein 2020-10-14 08:16:12 UTC 
Verified on CNV-2.5 (Oct 11 2020).
This warning message no longer displayed in VM import wizard, when picking "VMware" as provider.
This is though ConfigMap vmware-to-kubevirt-os in kube-public namespace is still missing.
Comment 5 errata-xmlrpc 2020-10-27 16:37:52 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 Container Platform 4.6 GA 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/RHBA-2020:4196
Note You need to log in before you can comment on or make changes to this bug.