Bug 1298293

Summary: v2v: import dialog - source VM list is not updated correctly.
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Sharon Gratch <sgratch>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.1CC: bugs, nsimsolo, tjelinek
Target Milestone: ovirt-4.0.0-rcFlags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
tjelinek: devel_ack+
rule-engine: testing_ack+
Target Release: 4.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-05 08:03:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
import dialog screenshot none

Description Nisim Simsolo 2016-01-13 16:39:08 UTC 
Description of problem:
webadmin Import VM dialog > "virtual machines on source" list is not updated correctly it it was loaded before.
For example, when loading the list using valid VMware details and afterward loading the list again with invalid details, the VMs in the list from the first load action are still listed instead of being cleaned from list.

Version-Release number of selected component (if applicable):
rhevm-3.6.2-0.1.el6
libvirt-client-1.2.17-13.el7_2.2.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.4.x86_64
vdsm-4.17.15-0.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Browse webadmin and navigate to virtual machines tab > import dialog.
2. Enter valid VMware parameters and click "load" button.
3. Enter incorrect VMware parameters and click "load" button.

Actual results:
"Virtual machines on source" list is still listed with VMs from the first load instead of being cleaned.

Expected results:
"Virtual machines on source" list shoud be updated in accordance to details entered and load action results. If it failed, the list should be cleared.

Additional info:
Screenshot attached.
Comment 1 Nisim Simsolo 2016-01-13 16:39:42 UTC 
Created attachment 1114465 [details]
import dialog screenshot
Comment 2 Sandro Bonazzola 2016-05-02 10:09:16 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 3 Yaniv Lavi 2016-05-23 13:24:57 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 4 Yaniv Lavi 2016-05-23 13:26:06 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 5 Sharon Gratch 2016-05-25 08:01:09 UTC 
The bug was opened for VMware only, but the fix was done for all other external sources also (OVA, XEN, KVM). So now all sources behave the same and in case  loading failed then both vms lists are cleaned.
Comment 6 Nisim Simsolo 2016-06-09 08:57:31 UTC 
Verification build: 
ovirt-engine-4.1.0-0.0.master.20160606111312.gitc7af584.el7

Verification scenario: 
1. Browse webadmin and navigate to virtual machines tab > import dialog.
2. Enter valid VMware parameters and click "load" button.
3. Enter incorrect VMware parameters and click "load" button, Verify "Virtual machines on source" pane is not listing any VM.
4. Enter different VMware environment details and click "load" button. Verify  
"Virtual machines on source" pane is listing new environment VMs correctly.
Comment 7 Sandro Bonazzola 2016-07-05 08:03:40 UTC 
oVirt 4.0.0 has been released, closing current release.