Description of problem: When cluster policy is set to evenly_distributed or vm_evenly_distributed proposed cluster is the same as current cluster. Does not matter if VMs are on the same or different host. Version-Release number of selected component (if applicable): vt2.2 How reproducible: 100% Steps to Reproduce: 1. Set cluster policy to evenly_distributed or vm_evenly_distributed 2. Run 2 VMs on different hosts, same host, other host... Actual results: Proposed cluster solution is the same as solution created by admin. No migration are proposed. Expected results: If two VMs are on the same host one should be maked to be migrated to other host. Additional info: In comparison power_saving cluster policy is working correctly.
Include logs and describe the setup (xml/json from restapi is probably enough).
Created attachment 937500 [details] console log of jbossAS, hosts.xml vms.xml of cluter
[0m[31m11:38:31,715 ERROR [org.quartz.core.JobRunShell] (oVirtOptimizerScheduler_Worker-1) Job DEFAULT.6da64b5bd2ee-039355ae-e4f6-44a7-918e-b9e3e2fff6c8 threw an unhandled Exception: : java.lang.OutOfMemoryError: Failed to create a thread: retVal -1073741830, errno 11 Quartz was not able to create a threat to collect current data from the engine. Increase the memory available to your JVM. But I guess the bug can be changed to RFE about better solver failure reporting.
This should be also stated in documentation for optimizer. Suggest user to add more memory for JVM.
Martin - what is the status of this issue? The patch attached is merged, what else is needed? better failure report? Can you detail exactly what is needed?
It can be closed, but as it is a downstream bug I need acks to process it properly.
Fixed bug tickets must have target milestone set prior to fixing them. Please set the correct milestone and move the bugs back to the previous status after this is corrected.
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
verified on : Red Hat Enterprise Virtualization Manager Version: 3.6.0.3-0.1.el6 verification steps: 1. on the optimizer VM, Reduce the memory on the JVM (change in /usr/share/jbossas/bin/standalone.conf this line to look like that JAVA_OPTS="-Xms256m -Xmx1024m ) 2. go to optimizer tab, you should see this message at first: Status: Connection to the optimizer is OK, but there is no solution for this cluster ans later you should see that the solution received