3.3. Red Hat Virtualization 4.0 Batch Update 2 (ovirt-4.0.5)

3.3.1. Enhancements

This release of Red Hat Virtualization features the following enhancements:
Previously, with the release of OpenStack Liberty the Open vSwitch agent ini file location changed. This caused host deployment to fail when the latest releases of OpenStack were used. Now, support for Liberty and newer releases of OpenStack has been added and host deployment no longer fails.
Previously, the current status of account lock was not displayed directly when showing user details using ovirt-aaa-jdbc-tool. The 'Account Unlocked At' date was compared with the current date and if 'Account Unlocked At' was set to future time the user account was locked. Now, the current status of account lock is displayed correctly. An "Account Locked' option with a boolean value has been added to the user details displayed by ovirt-aaa-jdbc-tools. 

For example: 
# ovirt-aaa-jdbc-tool user show user1
-- User user1(de506247-d1a1-4f16-94f3-0b83b0b236b2) -- 
  Account Disabled: false 
  Account Locked: true 
  Account Unlocked At: 2016-09-09 11:42:25Z
The latest virtio-win release which includes Windows 10 drivers is now required by Red Hat Virtualization Manager to ensure it will be upgraded.
With this update, the ability to import virtual machines from VMware, VMware OVA, XEN, and KVM via the Red Hat Virtualization REST API has been added. Previously, this was only possible using the web UI.
Red Hat Enterprise Linux 6 used mod_auth_kerb to setup Kerberos SSO, but this module has been deprecated; mod_auth_gssapi is used instead. This update ensures mod_auth_gssapi and mod_session is used, and that example configurations have been updated.

For existing customers, mod_auth_kerb will continue to work with previous versions of Red Hat Enterprise Virtualization.

3.3.2. Known Issues

These known issues exist in Red Hat Virtualization at this time:
A bug in oVirt Live ISO creation causes wrong SELinux labeling. Within the ISO, some files get the wrong context upon boot. 

This can be avoided by running oVirt Live in permissive mode; you can still use oVirt Live, but be aware that SELinux is not enforcing.
In bootstrap mode, prior to having the self-hosted engine storage domain imported, the Manager tells VDSM to disconnect the iSCSI target prior to attaching the master domain. The Manager doesn't know that hosted_storage is using the same target, as it is not in the database yet. 

As a result, VDSM disconnects the target, the Manager virtual machine loses connectivity to its disk, sanlock times out, and the Manager virtual machine is restarted.

To aviod this, do not use the same ISCSI target for the master domain and the hosted_storage domain.
Due to changes in devices within PPC64LE QEMU binary, it is not possible to live migrate a virtual machine started on Red Hat Enterprise Linux 7.2 to a Red Hat Enterprise Linux 7.3 host; the destination QEMU will reject the request. Such guests must be shut down and restarted on the destination host.

Virtual machines can be live migrated between hosts of the same Red Hat Enterprise Linux version. 

Virtual machines cannot be live migrated from a Red Hat Enterprise Linux 7.2 host to a Red Hat Enterprise Linux 7.3 host, or from a Red Hat Enterprise Linux 7.3 host to a Red Hat Enterprise Linux 7.2 host; the virtual machine must be shut down before migration.
The Disk Alignment feature is unavailable for PPC.