Description of problem: Due to bug 906213, vm will not be locked while creating the image, so vm start may happen while image is locked. 2013-01-30 19:47:57,410 beakerd ERROR Exception in exception handler :-( Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/bkr/server/tools/beakerd.py", line 477, in provision_virt_recipes manager.destroy_vm(system_name) File "/usr/lib/python2.6/site-packages/bkr/server/model.py", line 6672, in destroy_vm vm.delete() File "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/brokers.py", line 5092, in delete headers={"Correlation-Id":correlation_id}) File "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py", line 111, in delete return self.request('DELETE', url, body, headers) File "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py", line 128, in request last=last) File "/usr/lib/python2.6/site-packages/ovirtsdk/infrastructure/proxy.py", line 154, in __doRequest raise RequestError, response RequestError: status: 400 reason: Bad Request detail: Cannot remove VM: The disks guest_for_recipe_7_Disk1 are locked. Please try again in a few minutes. Version-Release number of selected component (if applicable): Beaker 0.11 + RHEV 3.1 How reproducible: 100% Steps to Reproduce: 1. Attach a RHEV 3.1 instance to beaker server 2. Create a job which can run with rhev guests Actual results: failed to schedule recipe with rhev guests due to start vm failure Expected results: job can run with rhev guests Additional info:
on gerrit: http://gerrit.beaker-project.org/#/c/1682/
Beaker 0.12 has been released.