Bug 1140763

Summary: [RFE] improve optimizer error reporting
Product: Red Hat Enterprise Virtualization Manager Reporter: Lukas Svaty <lsvaty>
Component: ovirt-optimizerAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: Shira Maximov <mshira>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: bgraveno, dfediuck, lsvaty, msivak, sherold, ylavi
Target Milestone: ovirt-3.6.0-rcKeywords: FutureFeature
Target Release: 3.6.0Flags: sherold: Triaged+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: ovirt-optimizer-0.9 Doc Type: Enhancement
Doc Text:
Error reporting in the ovirt-optimizer result report has been improved. It now differentiates between errors when there is no solution, no such cluster, and an empty solution.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-20 01:34:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1232536    
Attachments:
Description Flags
console log of jbossAS, hosts.xml vms.xml of cluter none

Description Lukas Svaty 2014-09-11 15:55:27 UTC 
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.
Comment 1 Martin Sivák 2014-09-12 08:34:43 UTC 
Include logs and describe the setup (xml/json from restapi is probably enough).
Comment 2 Lukas Svaty 2014-09-15 09:40:30 UTC 
Created attachment 937500 [details]
console log of jbossAS, hosts.xml vms.xml of cluter
Comment 3 Martin Sivák 2014-09-15 10:15:37 UTC 
[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.
Comment 4 Lukas Svaty 2014-09-15 10:17:35 UTC 
This should be also stated in documentation for optimizer. Suggest user to add more memory for JVM.
Comment 6 Yaniv Kaul 2015-11-19 21:07:54 UTC 
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?
Comment 7 Martin Sivák 2015-11-20 12:42:09 UTC 
It can be closed, but as it is a downstream bug I need acks to process it properly.
Comment 8 Red Hat Bugzilla Rules Engine 2015-11-20 12:42:11 UTC 
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.
Comment 9 Red Hat Bugzilla Rules Engine 2015-11-20 12:51:43 UTC 
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.
Comment 10 Shira Maximov 2015-11-24 15:43:30 UTC 
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