Should be a non-issue in 3.6.0. Moving to the scale team to verify.
Verified Was tested on VDSM 4.17.25, VDSM stayed up and did not restart during the procedure. Steps that where Reproduced: 1. created iscsi pools with 3 domains 100G each 2. created a wipe=true template (1GB disk) 3. created 3 pools from the template with 50 vm's on each pool 4. detach and remove the vm from each pool without waiting for previous pool to be deleted.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0660.html