Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1322602

Summary: python SDK: regenerate_ids does not have effect after udpate to RHEV 3.6.3.4-0.1.el6
Product: [oVirt] ovirt-engine Reporter: Michael Ablassmeier <ma>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.1.3CC: bugs, juan.hernandez, mgoldboi, tjelinek
Target Milestone: ovirt-3.6.6Keywords: Regression
Target Release: 3.6.6Flags: rule-engine: ovirt-3.6.z+
rule-engine: blocker+
mgoldboi: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-30 10:53:02 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:
Attachments:
Description Flags
python script none

Description Michael Ablassmeier 2016-03-30 21:05:02 UTC
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:

Comment 1 Juan Hernández 2016-03-31 09:17:59 UTC
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.

Comment 2 Red Hat Bugzilla Rules Engine 2016-03-31 09:18:04 UTC
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.

Comment 3 Juan Hernández 2016-03-31 09:24:29 UTC
May be a duplicate of bug 1294501, didn't check it.

Comment 4 Tomas Jelinek 2016-04-06 08:10:31 UTC
no, I don't think it is a duplicate, I think this is a different issue.

Comment 5 meital avital 2016-05-15 05:46:35 UTC
Verified on rhevm-3.6.6.2-0.1.el6