RHBA-2018:0562 - Bug Fix Advisory

Topic

An update for org.ovirt.engine-root is now available for Red Hat Virtualization Manager version 4.1.10

Description

Changes to the ovirt-engine component:

• Previously, when importing a virtual machine, if the vNIC profile mapping dialog was opened and canceled, the mapping was lost and the vNICs were not assigned a profile. In the current release, the default mapping that appears in the dialog is assigned to the vNICs when the import is complete. (BZ#1530565)
• In this release, the ENGINE_JBOSS_BLOCKING_TIMEOUT option, which changes the default value of jboss.as.management.blocking.timeout, is exposed. To change the default value, create "/etc/ovirt-engine/engine.conf.d/99-jboss-blocking-timeout.conf" with the line, "ENGINE_JBOSS_BLOCKING_TIMEOUT=NNN", where "NNN" is the number of seconds for the JBoss timeout. (BZ#1547031)
• Previously, if a virtual machine with a positive affinity to a host was down, the affinity rules enforcer tried to migrate it, because it was not running on the specified host. When migration failed, the affinity rules enforcer repeated tried to migrate the same virtual machine, ignoring other virtual machines that violated affinity rules. In this release, the affinity rules enforcer ignores virtual machines that are down. (BZ#1551582)
• Previously, Windows virtual machines configured to run in the PST timezone displayed an error alert in the Administration Portal. In the current release, this issue has been fixed and the error alert does not appear. (BZ#1552811)

Solution

For details on how to apply this update, which includes the changes described in this advisory, refer to:

Affected Products

• Red Hat Virtualization 4.1 x86_64
• Red Hat Virtualization Manager 4.1 x86_64

Fixes

• BZ - 1530223 - Template Seal option is not triggered via rest api in 4.1
• BZ - 1530565 - [downstream clone - 4.1.10] vNIC mapping is broken on import from data domain - vNICs mapped as 'Empty' in the destination cluster
• BZ - 1542886 - [downstream clone - 4.1.10] "Failed to determine the metadata devices of Storage Domain" error is shown for every storage domains in 4.1 environment with 4.0 hosts
• BZ - 1545598 - [downstream clone - 4.1.10] engine-setup should configure versionlock yum plugin to follow Obsoletes
• BZ - 1547031 - [downstream clone - 4.1.10] Very slow login to and very slow execution in the RHV Manager
• BZ - 1551582 - [downstream clone - 4.1.10] engine tries to balance vms that are down.
• BZ - 1552473 - [downstream clone - 4.1.10] Webadmin- Events - notification drawer- clear all alarms clear also all events
• BZ - 1552811 - [downstream clone - 4.1.10] "Actual Timezone in Guest Differs from Configuration Error" - PST / GMT -8 - Windows VM

CVEs

(none)

References

(none)