oVirt 3.6.6 Release Notes

The oVirt Project is pleased to announce the availability of oVirt 3.6.6 release as of May 23rd, 2016.

oVirt is an open source alternative to VMware vSphere, and provides an awesome KVM management interface for multi-node virtualization. This release is available now for Red Hat Enterprise Linux 6.7, CentOS Linux 6.7 (or similar) and Red Hat Enterprise Linux 7.2, CentOS Linux 7.2 (or similar).

To find out more about features which were added in previous oVirt releases, check out the previous versions release notes. For a general overview of oVirt, read the Quick Start Guide and the about oVirt page.

  1. oVirt 3.6.6 Release Notes
    1. Install / Upgrade from previous versions
      1. Fedora / CentOS / RHEL
      2. oVirt Hosted Engine
      3. oVirt Live
      4. oVirt Node
    2. What's New in 3.6.6?
      1. Enhancement
        1. oVirt Engine
        2. oVirt Hosted Engine Setup
      2. Release Note
        1. VDSM
    3. Bug fixes
      1. oVirt Engine
      2. VDSM
      3. VDSM JSON-RPC Java
      4. oVirt Hosted Engine Setup
      5. oVirt Hosted Engine HA
      6. oVirt vmconsole
      7. oVirt Engine Extension AAA JDBC
      8. oVirt Node

Install / Upgrade from previous versions

Fedora / CentOS / RHEL

In order to install it on a clean system, you need to install

# yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm

If you are upgrading from a previous version, you may have the ovirt-release35 package already installed on your system. You can then install ovirt-release36.rpm as in a clean install side-by-side.

Once ovirt-release36 package is installed, you will have the ovirt-3.6-stable repository and any other repository needed for satisfying dependencies enabled by default.

If you're installing oVirt 3.6.6 on a clean host, you should read our Quick Start Guide.

If you are upgrading from oVirt < 3.5.0, you must first upgrade to oVirt 3.5.0 or later. Please see oVirt 3.5.6 Release Notes for upgrade instructions.

For upgrading now you just need to execute:

  # yum update "ovirt-engine-setup*"
  # engine-setup

oVirt Hosted Engine

If you're going to install oVirt as Hosted Engine on a clean system please follow Hosted_Engine_Howto#Fresh_Install guide.

If you're upgrading an existing Hosted Engine setup, please follow Hosted_Engine_Howto#Upgrade_Hosted_Engine guide.

oVirt Live

A new oVirt Live ISO is available at:

http://resources.ovirt.org/pub/ovirt-3.6/iso/ovirt-live/

oVirt Node

A new oVirt Node installation iso is available at: http://resources.ovirt.org/pub/ovirt-3.6/iso/ovirt-node-ng-installer/

Download and install instructions are avaialble on the Node Project page.

If you have already got oVirt Node Next installed, you can run

yum update

to update Node.

What's New in 3.6.6?

Enhancement

oVirt Engine

  • BZ 1241149 [RFE] Provide way to preform in-cluster upgrade of hosts from el6->el7.
  • BZ 1332463 [RFE] restore: ensure that 3.6 on el6 backup can be restored on 3.6 on el7
    Feature:

    Allow engine-backup on el7 to restore backups taken on el6.

    Reason:

    engine 4.0 does not support el6. Users that want to upgrade from 3.6 on el6 to 4.0 on el7 have to do this by backing up the engine on 3.6/el6 and restore on 4.0/el7.

    This feature, backported from 4.0, allows to do such a migration also in 3.6.

    Result:

    Using this flow, it's possible to migrate a el6 setup to el7:

    On the existing engine machine run:
    1. engine-backup --mode=backup --file=engine-3.6.bck --log=backup.log

    On a new el7 machine:
    2. Install engine, including dwh if it was set up on el6.
    3. Copy engine-3.6.bck to the el7 machine
    4. engine-backup --mode=restore --file=engine-3.6.bck --log=restore.log --provision-db --no-restore-permissions
    5. engine-setup

    Check engine-backup documentation for other options, including using remote databases, extra grants/permissions, etc.

oVirt Hosted Engine Setup

  • BZ 1324520 [RFE] Allow to skip tty check to allow for unattended install via Ansible

Release Note

VDSM

  • BZ 1323952 Change migration parameters
    migration behavior changes - newly there will be only at most 2 migrations started(instead of 3) in parallel, at higher speed, to increase the chances that migrations converge instead of timing out.
    Values can be changed back or to any other value in vdsm.conf

Bug fixes

oVirt Engine

  • BZ 1142865 Missing QoS in the warning that is shown when removing multiple QoS
  • BZ 1143869 Impossible to limit access to CPU profiles via user WEBUI portal on user/group basis.
  • BZ 1190142 New Template dialog to narrow when quota is enabled
  • BZ 1284472 User can't create a VM. No permission for EDIT_ADMIN_VM_PROPERTIES
  • BZ 1292398 Block restore memory on newer compatibility versions
  • BZ 1303160 Connecting vfio-pci device failed, no device found with kernel > 3.10.0-229.20.1.el7.x86_64 (RHEL 7.2)
  • BZ 1305330 Disable high availability option for hosted engine VM
  • BZ 1311121 oVirt system tests for 3.6 fail to deactivate domain on the first try - race with storage domain status syncing process
  • BZ 1311151 [Hosted-engine] - The vNIC(vnet0) of the HostedEngine VM reported as unplugged in UI although it is actually UP in the guest
  • BZ 1314417 [webAdmin] Edit VM name validation failure do not direct the General tab
  • BZ 1314426 Edit VM hotplug show redundant change list
  • BZ 1314781 Add Cockpit port to the default ports to be opened when Engine manages the firewall
  • BZ 1316853 Cloning a VM from a cloned cinder disk results in a locked image status
  • BZ 1317473 [admin portal] Increase CPUs number in VM edit dialog of running VM is not propagated to virtual sockets
  • BZ 1318050 Livemerge Cannot remove Snapshot. Low disk space on Storage Domain
  • BZ 1320128 Host setup fails - network disconnection causes SetupNetwork not to be sent (or not received by host)
  • BZ 1320594 enable hyperv optimizations by default
  • BZ 1320606 Host deploys fails - ping flood issue on VDSM side
  • BZ 1321249 ovirt-engine-tools-backup dependency error
  • BZ 1322602 python SDK: regenerate_ids does not have effect after udpate to RHEV 3.6.3.4-0.1.el6
  • BZ 1323462 Local export storage domain metadata states Version 3 instead of Version 0, making it impossible to re-attach.
  • BZ 1324363 [REST-API] Copy of template disk doesn't complete nicely
  • BZ 1324733 [z-stream clone - 3.6.6] engine-setup stage 'Setup validation' takes too long to complete
  • BZ 1324935 [REST API] Missing href field for sshpublickey
  • BZ 1326311 Getting exception while trying to open Edit dialog while the VM is starting
  • BZ 1326511 remove "supported browser" alert
  • BZ 1328036 ovirt-vmconsole conf and pki are not backed up
  • BZ 1329317 Host hangs indefinitely in "Installing" stage during host-deploy
  • BZ 1330483 [z-stream clone - 3.6.6] Storage domain ownership of LUN not displayed.
  • BZ 1330742 [AAA] After AAA configuration, users unable to login via scripts
  • BZ 1332088 [3.6.6 clone][migration 3.6 el6 - 3.6 el7] Failed to execute stage 'Setup validation': Firewall manager iptables is not available

VDSM

  • BZ 1264003 CPU which goes offline while vdsm is running breaks getVdsStats
  • BZ 1322842 VM with a payload doesn't start with libvirt >= 1.3.2
  • BZ 1325485 [3.6 only] SCSI pass through [via hook] does not work
  • BZ 1332038 [z-stream clone - 3.6.6] After a live merge failure, a VM with volumes in an illegal state can be restarted

VDSM JSON-RPC Java

  • BZ 1323465 Setup Networks cause ClosedChannelException

oVirt Hosted Engine Setup

  • BZ 1322729 Hosted-engine-setup still requires to copy the answerfile from the first host via scp

oVirt Hosted Engine HA

  • BZ 1327516 Infinite loop trying to fix remote path on glusterFS storage domain
  • BZ 1332963 IOError from smtplib is not handled

oVirt vmconsole

  • BZ 1329657 %pre (and anaconda) fails when installing on a system without shadow-utils

oVirt Engine Extension AAA JDBC

  • BZ 1304368 aaa-jdbc return only direct group membership, not indirect membership

oVirt Node

  • This is the first release which provides oVirt Node Next, see node for more details.