Bug 1298293 - v2v: import dialog - source VM list is not updated correctly.
Summary: v2v: import dialog - source VM list is not updated correctly.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Sharon Gratch
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-13 16:39 UTC by Nisim Simsolo
Modified: 2016-07-05 08:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-05 08:03:40 UTC
oVirt Team: Virt
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
tjelinek: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)
import dialog screenshot (147.52 KB, image/png)
2016-01-13 16:39 UTC, Nisim Simsolo 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 57841 0 master MERGED webadmin: v2v-source vms list is cleaned in failure 2016-05-25 06:42:30 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.