Red Hat Bugzilla – Bug 1252759
[virt-v2v] Import a VM using virt-v2v of a VM which is currently in lock status will cause an uninitialzed CDA message
Last modified: 2016-02-18 06:15:32 EST
Created attachment 1061854 [details]
Description of problem:
Import a VM using virt-v2v of a VM which is currently in the process of import (The VM is in lock status) will present a message with uninitialzed keys (attached message)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Import a VM from v2v
2. Once the VM is being imported in lock status, try to import it again
an uninitialized message will be performed
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.
Arik, this doesn't seem to be in 3.6
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA
Verified using build:
1. Import VMware VM
2. When import phase changed to "initialize" phase or further, try to import the same VM again.
3. Verify in second import dialog that clone checkbox is checked and grayed out (cannot be changed).
4. Click "OK" and verify that the next "operation canceled" message appears:
"Import VM failed - VM Name already exist in the system. Please rename the VM in the system first"