Created attachment 1141937 [details] python script Description of problem: For our Customers we provide a backup and restore module for RHEV virtual machines. During restore the virtual machine is created from the saved configuration file. According to the ovirtsdk documentation if setting the params initialization option "regenerate_ids" one should be able to create a VM which ID is generated during creation. This worked up to RHEV Version 3.5.8, but after updating our internal test system the option does not have any effect anymore. It complains about the virtual machine beeing already existant. Attached is a test python script which creates a virtual machine from a xml configuration file. If the virtual machine with the ID already exists it exits with: Import VM failed - VM Id already exist in the system. Please remove the VM (client_small) from the system first even tho the option is set. Iam not sure if this is the right place, as i dont think the issue is in ovirt sdk (i tried with the old SDK for version 3.5 and 3.6) but in the backend, but i dont know where to report this problem, reassing as needed, thanks! Version-Release number of selected component (if applicable): RHEVM: 3.6.3.4-0.1.el6 SDK: rhevm-sdk-python-3.6.3.0-1.el6ev.noarch How reproducible: See attached python script Steps to Reproduce: 1. Execute attached python script 2. 3. Actual results: Complains about VM beeing existant Expected results: Should create VM with newly generated ID Additional info:
I believe that this regression was introduced by the following change: core: in-memory lock for imported vm https://gerrit.ovirt.org/38032 As a result of this change the assignment of a new id to the imported virtual machine only happens if the parameters passed contain the "regenerateIds" and "vmId" parameters.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
May be a duplicate of bug 1294501, didn't check it.
no, I don't think it is a duplicate, I think this is a different issue.
Verified on rhevm-3.6.6.2-0.1.el6