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
Created attachment 1372738 [details] rename-after
Created attachment 1372739 [details] vdsm.log
Created attachment 1372740 [details] engine.log
seems like a more general problem with mapping properties for multiple VMs during import from any provider
*** Bug 1540877 has been marked as a duplicate of this bug. ***
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.
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.