Created attachment 706021 [details] vdsm log Description of problem: After the test finish we tried to remove all created datacenters. We started with removing VMs, then removed VM template (which finished with success), then tried to deactivate master storage domain. The last operation failed because there was still some tasks on pool. The only remaining task was task with id ebf41dcd-ebf7-4217-ad37-83787b97b978, 'deleteImage' invoked during removing VM template. Task was actually finished, but was not removed from the pool (was removed some miliseconds later). Version-Release number of selected component (if applicable): SI27.3 How reproducible: http://jenkins.qa.lab.tlv.redhat.com:8080/view/Storage/view/3.1/job/3.1-storage_direct-lun_sanity-iscsi-rest/226/ Steps to Reproduce: 1. create an iSCSI datacenter 2. create a VM 3. stop the VM 4. attach a disk to the VM 5. start and stop the VM 6. create a template based on the VM, wait until it is created 7. remove the VM 8. remove the template 9. try to deactivate master storage domain The last step should be done right after the previous one Actual results: Deactivation of the master storage domain failed. Expected results: Deactivation should pass, tasks related to a template should be removed from the pool before template is reported as removed. Additional info:
Created attachment 706022 [details] engine log
The object no longer exists per se, but in the background we're going on freeing up the space this is not a bug. In fact going forward we want 'delete' to be just a removal of a tag (subsecond) in vdsm and then in the background vdsm will go on clearing things up. Since these operations are potentially (very) long yet do not require blocking other operations this is the expected behaviour. When moving the domain to maintenance you need to track the correct thing (check there are no tasks) and not assume specific implementation. Tasks are not necessarily tied to specific objects (general maintenance tasks).
*** Bug 920220 has been marked as a duplicate of this bug. ***
Ayal, its indeed a bug, duplicate of BZ916652 *** This bug has been marked as a duplicate of bug 916652 ***