Hide Forgot
Hi, the following bug is opened in order to perform a tracking for integration team. It will track different checks which are done for new locking mechanism in engine. First stage is: The changes are the following: 1. Replace default lock mechanism 2. Some small updates in ActivateStorageDomain, RemoveVM, AddStoragePoolWithStoragesCommand Please recheck that following change did not cause to regression in the following scenario and in general . (It is also describe at pre-integration ticket: https://trac.qa.lab.tlv.redhat.com/trac/integration/ticket/557)
Created attachment 549182 [details] Patch
Testing progress: - create pool - create storage domain - create vm - create volume - move vm from one storage to another - null pointer exception * http://pastebin.test.redhat.com/71971 - create vm from template (clone) - null pointer exception: * http://pastebin.test.redhat.com/71973 - migrate master domain - migrate master with restarting vdsm on spm host - suspend - create snapshot - preview - commit - delete snapshot (merge) - multiple actions: * delete template & from different session create vm from template * activate storage domain & from different session detach storage domain * suspend vm and from different session take vm down * move vm and from different session delete vm locking mechanism works as expected.
Created attachment 549818 [details] Storage patch
A new patch should introduce an using of lock util inside storage flows. Please check different storage scenarious, including fail over , sententious creation, attaching, removing, reconstruct etc on storage
Created attachment 549819 [details] Storage patch Correct One
Please use a last storage patch a previous one missing one file
I think you missed a negative test, like when you try to create a snapshot and failed on CanDoAction and lock was not released and possible any other similar scenarious
The process was changed again no need for bug