RHBA-2016:0427 - Bug Fix Advisory

Topic

Updated ovirt-optimizer packages that fix several bugs and add various enhancements are now available.

Description

The Optimizer is a load balancing service that analyzes the memory usage of hosts in a particular cluster, and provides a suggested set of virtual machine migrations that will enable optimal virtual machine deployment across hosts. This is useful in situations where a virtual machine cannot be started due to insufficient resources. The Optimizer calculates a load balancing solution every 30 seconds, which is displayed in a sub-tab for each cluster. To avoid conflicts caused by sharing memory and CPU, the Optimizer is hosted on a machine that is separate from the Red Hat Enterprise Virtualization Manager. The Optimizer communicates with the Manager through the Manager's REST API.

Changes to the ovirt-optimizer component:

• With this enhancement, many fixes and enhancements were included in the optimization rules. For example, the PinToHost rule, rules for the self-hosted engine, and support for custom rules have been added. (BZ#1219039)
• Previously, the default configuration for jQuery requests did not time out. If incoming and outgoing connections to the Optimizer machine were blocked from the Manager, there were no indications that the connections were blocked. With this update, the UI plug-in reports an error if the Optimizer machine can not be reached within 60 seconds. (BZ#1173540)
• Previously, the Optimizer UI plug-in used a different API to authenticate. As a result, users were prompted to log in again when navigating to the optimization field in the Clusters tab. With this update, the Optimizer UI plug-in reuses the Administration Portal login credentials, and does not prompt users to log in again. (BZ#1172978)
• Previously, when users executed a solution step suggested by the Optimizer, if the solution wasn't doable, an error message was returned. This was confusing for users. With this update, if the full solution is not doable, the solution is still displayed but grayed out so it is clear to users that the full solution is not possible to implement at the time. Users can still read the suggested solution and manually implement parts of the solution that are doable. (BZ#1173551)
• Previously, the Optimizer machine performed a new login to the Manager every time it fetched data from the Manager. As a result, the log was swamped with recurring admin@internal login entries. With this update, the Optimizer machine now properly creates a session and uses the session key for subsequent authentication. (BZ#1246118)

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

For details on how to apply this update, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat Virtualization 3.6 x86_64

Fixes

• BZ - 1140293 - Uninformative status while data is not recieved by optimizer
• BZ - 1172978 - ovirt-optimizer-ui plugins asks for rest credentials after plugin tab is opened
• BZ - 1173117 - Optimizer suggest migrating VMs which does not allow migration
• BZ - 1173540 - No timeout and error status when optimizer machine is blocked by iptables from engine machine
• BZ - 1173551 - Optimizer should not propose steps if solution is not doable
• BZ - 1219039 - Performance and usability updates for ovirt-optimizer preview version
• BZ - 1246118 - recurring admin@internal logged in messages in events when using Optimizer

CVEs

(none)

References

• http://www.redhat.com/security/updates/classification/#normal