Issued:
2017-07-06
Updated:
2017-07-17

RHEA-2017:1692 - Red Hat Virtualization Manager ovirt-engine - 4.1.3


Synopsis

Red Hat Virtualization Manager (ovirt-engine) 4.1.3

Type/Severity

Product Enhancement Advisory None

Topic

An update is now available for Red Hat Virtualization Manager.

Description

The Red Hat Virtualization Manager is a centralized management platform that allows system administrators to view and manage virtual machines. The Manager provides a comprehensive range of features including search capabilities, resource management, live migrations, and virtual infrastructure provisioning.

The Manager is a JBoss Application Server application that provides several interfaces for accessing and interacting with the virtual environment, including an Administration Portal, a User Portal, and a Representational State Transfer (REST) Application Programming Interface (API).

Changes to the ovirt-engine component:

  • Previously, after restoring from backup the Manager occasionally attempted to start an already running virtual machine again automatically as the Manager believed the virtual machine was down and this caused a second instance of the virtual machine to start on a different host. Now, the virtual machine status is set to down and the exit status is set to unknown after restoring from a backup. This status is changed as soon as the virtual machine is run. This means that the automatic restart of the virtual machine is no longer attempted. (BZ#1446055)

  • With this update, an issue where the 'Use already configured password' option was unavailable when creating a new virtual machine from a template that had the cloudinit root password stored has been fixed. This issue meant that the creation of the new virtual machine succeeded but the password was not copied. (BZ#1463597)

  • With this update, the user can now control the location of the temporary directory that the engine-backup command creates. The command line option --tmpdir=DIR and the variable $TMPDIR have been added to control the location of the temporary directory. Previously, the engine-backup command always used /tmp. If /tmp was full, or close to being full, it was not possible to tell the engine-backup command to use a different directory. Now, it is possible to run the engine-backup command even if the /tmp directory is full by telling the engine-backup command to use a different location. (BZ#1445631)

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/2974891

Affected Products

ProductVersionArch
Red Hat Virtualization4.1x86_64

Updated Packages

  • ovirt-engine-extensions-api-impl-javadoc-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-setup-plugin-websocket-proxy-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-extensions-api-impl-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-setup-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-setup-plugin-ovirt-engine-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-webadmin-portal-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-setup-plugin-ovirt-engine-common-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-backend-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-tools-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-userportal-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-4.1.3.5-0.1.el7.src.rpm
  • ovirt-engine-vmconsole-proxy-helper-4.1.3.5-0.1.el7.noarch.rpm
  • rhevm-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-dbscripts-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-tools-backup-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-lib-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-restapi-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-setup-base-4.1.3.5-0.1.el7.noarch.rpm
  • ovirt-engine-websocket-proxy-4.1.3.5-0.1.el7.noarch.rpm

Fixes

CVEs

(none)

References

(none)


Additional information