Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1710932

Summary: [v2v][UI] Import VM: Once operating system is picked, Operating system for another VM is not detected
Product: OpenShift Container Platform Reporter: Ilanit Stein <istein>
Component: Console Kubevirt PluginAssignee: Filip Krepinsky <fkrepins>
Status: CLOSED ERRATA QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aos-bugs, cnv-qe-bugs, gouyang, mlibra, ncredi, rawagner, sgordon
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.0.0-14.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-24 20:16:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ilanit Stein 2019-05-16 15:21:31 UTC
Description of problem:
In UI, Create VM wizard dialog, provision source: Import,
choose VMware provider, pick a RHEL7 VM - 
Under the operating system, it is mentioned that RHEL 7 os was detected.
pick in the Operating system drop down "RHEL 7".

Then, while in the same window, pick another VM, with Windows OS.
The Operating System field is not zeroed, and still remain RHEL7.
No detected OS is displayed, under the Operating System field.

Version-Release number of selected component (if applicable):
v.2.0.0-12


Expected results:
In case Operating system is picked for one VM, in case another VM is picked,
the Operating system should be zeroed, and the detected Operating system should be displayed.

Comment 3 Marek Libra 2019-06-03 10:00:40 UTC
Included in kubevirt-2.0.0-14.6 .
Will be in hco-bundle-registry:v2.0.0-22 .

Comment 6 errata-xmlrpc 2019-07-24 20:16:06 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, 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-2019:1850