Created attachment 889259 [details] engine.log Description of problem: When there seems to be not enough memory available to run a VM, when aquiring a VM from a pool causes confusing dialog which does not mention memory/resources problem but mistakenly directs an user to debug around pool configuration (number of pooled vms...). Thus I would expect resources error. ---%--- Error while executing action: ad-w2k8r2: Cannot allocate and run VM from VM-Pool. There are no available VMs in the VM-Pool. ---%--- Version-Release number of selected component (if applicable): rhevm-userportal-3.4.0-0.13.beta3.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. have a pool with more vms 2. run some vms on a host so there won't be free memory to run a pooled vm 3. aquire a pool vm while clicking on pool icon in user portal Actual results: confusing error Expected results: show right error about the issue why pooled vm acquisition did not work Additional info:
I'd add a generic sentence about possible insufficient resources. We don't want to put exact troubleshooting error in the user portal, I guess...
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know
There was a bug that we return this general error instead of specific error for VM in a pool. bz 1259244 solve it *** This bug has been marked as a duplicate of bug 1259244 ***