Description of problem: In case of adding a VM to a Vmpool, while VM was not finished to be created (still locked), detach the VM from Vmpool is possible, and then, when the VM creation is finished, the VM is added back to the pool. This problem fail the VMs automatic test, with flow: 1. Add vm to a VMpool 2. Detach all vms (while VM is still in locked status) 3. Try to remove vmpool => fail since there is a VM attached to the Vmpool. Version-Release number of selected component (if applicable): vt10.1 Expected results: Block detach of VM from Vmpool, if it still under creation process.
shmuel, can you please re-check if this is relevant after the new implementation of pool removal?
Done. See the change on Gerrit.
Verified rhevm-3.6.0.1-0.1.el6.noarch. tested according to description. Detaching vm from pool while vm image is still locked is blocked. Remove pool is also blocked until vms are created. There is a problem with formatting the error message that's invoked when you try to delete the pool when vm's are still created. I get: Cannot ${action} ${type}. This VM Pool is currently in use to create VM ${VmName}. Let me know if there's an open bz on this one and if not I shall open one.
(In reply to sefi litmanovich from comment #3) > There is a problem with formatting the error message that's invoked when you > try to delete the pool when vm's are still created. I get: > > Cannot ${action} ${type}. This VM Pool is currently in use to create VM > ${VmName}. > > Let me know if there's an open bz on this one and if not I shall open one. Bug 1255590 describes the same problem.