Bug 1529248

Summary: Can't change individual properties of guest when importing multiple VMs from vmware/kvm/xen/ova/exportdomain
Product: [oVirt] ovirt-engine Reporter: mxie <mxie>
Component: Backend.CoreAssignee: Sharon Gratch <sgratch>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0.2CC: bugs, juzhou, kuwei, lveyde, mavital, michal.skrivanek, mzhan, nsimsolo, tjelinek, tzheng, xiaodwan
Target Milestone: ovirt-4.2.2Flags: tjelinek: ovirt-4.2?
tjelinek: planning_ack?
rule-engine: devel_ack+
mavital: testing_ack+
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.4 Doc Type: Bug Fix
Doc Text:
Fix the UI v2v dialog behavior to enable changing name and os values for the imported vms (one or more) while importing from external providers and also enable changing vm name value for the imported vms (one or more) while importing from export domain. The new changed field value will be kept even if switching between import dialog sub-tabs or import vms list and will be reset to original value once you return to previous 1'st v2v dialog.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-05 09:38:11 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:
Bug Depends On:    
Bug Blocks: 1049604    
Attachments:
Description Flags
rename-before
none
rename-after
none
vdsm.log
none
engine.log none

Description mxie@redhat.com 2017-12-27 10:04:49 UTC
Created attachment 1372737 [details]
rename-before

Description of problem:
Can't rename guest if import guest from vmware/kvm/xen at rhv4.2 GUI 

Version-Release number of selected component (if applicable):
RHV:4.2.0.2-0.1.el7
vdsm-4.20.9.3-1.el7ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Import guest from vmware at rhv4.2 GUI 
Login rhv4.2 -> click dashboard-> click virtual machine -> select import -> choose "vmware as source" and input vmware info-> load guests succesfully -> select a guest to import

2.Try to rename guest as screenshot"rename-before", then click ok to import guest

3.Found the name of guest doesn't change after importing, pls refer to screenshot "rename-after"

4.Also can't rename guest if import guest from kvm/xen at rhv4.2 GUI 

5.Can rename guest if import guest from export domain at rhv4.2 GUI 

Actual results:
As above description

Expected results:
Could rename guest at interface of importing guest at rhv4.2 GUI 

Additional info:
Can't reproduce this problem on rhv4.1 and vdsm-4.19.34-1.el7ev.x86_64

Comment 1 mxie@redhat.com 2017-12-27 10:05:25 UTC
Created attachment 1372738 [details]
rename-after

Comment 2 mxie@redhat.com 2017-12-27 10:06:59 UTC
Created attachment 1372739 [details]
vdsm.log

Comment 3 mxie@redhat.com 2017-12-27 10:07:37 UTC
Created attachment 1372740 [details]
engine.log

Comment 4 Michal Skrivanek 2018-02-01 12:12:39 UTC
seems like a more general problem with mapping properties for multiple VMs during import from any provider

Comment 5 Sharon Gratch 2018-03-06 09:37:44 UTC
*** Bug 1540877 has been marked as a duplicate of this bug. ***

Comment 8 meital avital 2018-04-02 14:26:49 UTC
verification version:
rhvm-4.2.2.6-0.1.el7
libvirt-client-3.9.0-14.el7_5.2.x86_64
qemu-kvm-rhev-2.10.0-21.el7_5.1.x86_64
vdsm-4.20.23-1.el7ev.x86_64
virt-v2v-1.36.10-6.el7.x86_64

Verification scenario:
1. Browse Webadmin -> Import dialog -> select VMware provider -> click "load" -> Select 5 VMs and continue to second import dialog
2. Rename each VM to 1-5 and set matching OS type. select some of them to be imported as clone.
3. Skip between VM tabs and between selected VMs few times. Verify changes from step 2 are kept.
4. Click OK and verify all VMs imported successfully, VM naming and OS type is according to step 2 changes.
5. Run VMs and verify VMs are running.
6. repeat steps 1-5 this time import from KVM and Xen environments.

Comment 9 Sandro Bonazzola 2018-04-05 09:38:11 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.