oVirt 4.3.0 Release Notes

The oVirt Project is pleased to announce the availability of the 4.3.0 release as of February 04, 2019.

oVirt is a free open-source distributed virtualization solution, designed to manage your entire enterprise infrastructure. oVirt uses the trusted KVM hypervisor and is built upon several other community projects, including libvirt, Gluster, PatternFly, and Ansible.

This release is available now for Red Hat Enterprise Linux 7.6, CentOS Linux 7.6 (or similar).

If you’d like to try oVirt as quickly as possible, follow the instructions on the Download page.

For complete installation, administration, and usage instructions, see the oVirt Documentation.

For a general overview of oVirt, read the About oVirt page.

To learn about features introduced before 4.3.0, see the release notes for previous versions.

EPEL

Don’t enable all of EPEL on oVirt machines.

The ovirt-release package enables the EPEL repositories and includes several specific packages that are required from there. It also enables and uses the CentOS SIG repos, for other packages.

If you want to use other packages from EPEL, you should make sure to use includepkgs and add only those you need avoiding to override packages from other repos.

Known Issues

Bug 1672587 - VNC encryption is true on host after upgrade causing “Unsupported security types: 19” causes VNC console to be broken. As a workaround, disable the vnc_tls flag on the Host and restart libvirt, or use SPICE. See the BZ for details.

Bug 1662047 – [UI] 2 dashboard icons after upgrade causes 2 dashboard icons after upgrade. An async fix has already been published. New standalone and hosted engine upgrades will catch the fix. If you have already upgraded to 4.3.0 and see the issue, run yum update and engine-setup on your Engine.

What’s New in 4.3.0?

Release Note

VDSM

BZ 1655115 Drop 3.6 and 4.0 datacenter/cluster level

The current release removes the VDSM daemon’s support for cluster levels 3.6/4.0 and Red Hat Virtualization Manager 3.6/4.0. This means that VDSM from RHV 4.3 cannot be used with the Manager from RHV 3.6/4.0. To use the new version of VDSM, upgrade the Manager to version 4.1 or higher.

The current release removes the VDSM daemon’s support for cluster levels 3.6/4.0 and Red Hat Virtualization Manager 3.6/4.0. This means that VDSM from RHV 4.3 cannot be used with the Manager from RHV 3.6/4.0. To use the new version of VDSM, upgrade the Manager to version 4.1 or higher. BZ 1514004 [downstream clone - 4.3.0] [RFE] Drop TLSv1 and TLSv1.1 encryption protocols support

The TLSv1 and TLSv1.1 protocols are no longer secure. They have been forcefully disabled in the VDSM configuration and cannot be enabled.



Only TLSv1.2 and higher versions of the protocol are enabled. The exact version enabled depends on the underlying OpenSSL version.

oVirt Engine

BZ 1627756 On engine side replace fluentd dependencies with rsyslog

The current release replaces Fluentd with Rsyslog for collecting oVirt logs and collectd metrics. Systems running Red Hat Virtualization Manager and upgraded from 4.2 will still have Fluentd installed but it will be disabled and stopped.

After upgrading to 4.3, you can remove the Fluentd packages.

The current release replaces Fluentd with Rsyslog for collecting oVirt logs and collectd metrics. Systems running Red Hat Virtualization Manager and upgraded from 4.2 will still have Fluentd installed but it will be disabled and stopped. After upgrading to 4.3, you can remove the Fluentd packages. BZ 1550634 Drop 3.6 and 4.0 datacenter/cluster level

This release removes the Red Hat Virtualization Manager support for clusters levels 3.6 and 4.0. Customers must upgrade their data centers to Red Hat Virtualization Manager 4.1 or later before upgrading to Red Hat Virtualization Manager 4.3.

This release removes the Red Hat Virtualization Manager support for clusters levels 3.6 and 4.0. Customers must upgrade their data centers to Red Hat Virtualization Manager 4.1 or later before upgrading to Red Hat Virtualization Manager 4.3. BZ 1599321 Config values inconsistency between RHV versions

There are inconsistencies in the following internal configuration options:

- HotPlugCpuSupported

- HotUnplugCpuSupported

- HotPlugMemorySupported

- HotUnplugMemorySupported

- IsMigrationSupported

- IsMemorySnapshotSupported

- IsSuspendSupported

- ClusterRequiredRngSourcesDefault

Systems that have upgraded from RHV 4.0 to RHV 4.1/4.2 and are experiencing problems with these features should upgrade to RHV 4.2.5 or later.

There are inconsistencies in the following internal configuration options: - HotPlugCpuSupported - HotUnplugCpuSupported - HotPlugMemorySupported - HotUnplugMemorySupported - IsMigrationSupported - IsMemorySnapshotSupported - IsSuspendSupported - ClusterRequiredRngSourcesDefault Systems that have upgraded from RHV 4.0 to RHV 4.1/4.2 and are experiencing problems with these features should upgrade to RHV 4.2.5 or later. BZ 1651220 Require Ansible 2.7+

This release adds a requirement for Ansible version 2.7, the lowest version required to run oVirt Ansible roles.

oVirt Host Dependencies

BZ 1627753 On hosts replace fluentd dependencies with rsyslog

The current release replaces Fluentd with Rsyslog for collecting oVirt logs and collectd metrics.

Hosts upgraded from 4.2 will still have Fluentd installed, but the service is disabled and stopped.

After upgrading to 4.3, you can remove the fluentd packages.

oVirt Release Package

BZ 1609884 ovirt-release-master for centos doesn’t contain current ovirt-web-ui

In this release, the oVirt release package for master, ovirt-release-master, enables a new repository hosted on the Cool Other Package Repositories (COPR) service for delivering ovirt-web-ui packages.

Enhancements

VDSM

BZ 1644693 High Host CPU load for Windows 10 Guests (Update 1803) when idle

Feature: Added enlightenment support in order to reduce CPU load by enabling the hyper-visor synic and stimer states.



Reason: To improve performance when running Windows as a guest OS.



Result: Anticipated results are that CPU load will be reduced to 0-5% on Linux Virtual Machines.

Feature: Added enlightenment support in order to reduce CPU load by enabling the hyper-visor synic and stimer states. Reason: To improve performance when running Windows as a guest OS. Result: Anticipated results are that CPU load will be reduced to 0-5% on Linux Virtual Machines. BZ 1641125 [RFE] add a configuration policy for vGPU placement

It is now possible to set in host configuration preferred vGPU placement on physical cards. Separated placement prefers putting each vGPU on a separate physical card, consolidated placement prefers putting more vGPUs on available physical cards.

It is now possible to set in host configuration preferred vGPU placement on physical cards. Separated placement prefers putting each vGPU on a separate physical card, consolidated placement prefers putting more vGPUs on available physical cards. BZ 1598391 [RFE] - Certify OSP 14 with OVN as an external network provider on RHV 4.3

Neutron from OSP 14 configured to use OVN can be used as an external network provider on RHV 4.3 with the limitation described in bug 1655906 .

Neutron from OSP 14 configured to use OVN can be used as an external network provider on RHV 4.3 with the limitation described in bug 1655906 . BZ 1625612 [RHV] failed to convert VMware ESX VM with snapshot

Feature: Removes the code within the VDSM blocking the importing of VMWare VMs with snap shots in order to take advantage of virt-v2v support for importing these types of VMs that was added to the virt-v2v-1.36.10-6.el7.x86_64.rpm package.



Reason: We would like to expose this feature for use by oVirt users.



Result: oVirt now supports the importing of VMware VMs that include snap shots.

Feature: Removes the code within the VDSM blocking the importing of VMWare VMs with snap shots in order to take advantage of virt-v2v support for importing these types of VMs that was added to the virt-v2v-1.36.10-6.el7.x86_64.rpm package. Reason: We would like to expose this feature for use by oVirt users. Result: oVirt now supports the importing of VMware VMs that include snap shots. BZ 1587892 After importing KVM VM the actual size is bigger than the virtual size

Feature:



Added KVM Sparseness support to KVM to oVirt Virtual Machine Importing so that when Thin Provisioning is enabled, the Disk Size of the original KVM Image will be preserved after importing to oVirt.



Reason:



Unless the user specifically specifies pre-allocation, the Disk Size of the Virtual Machine should be no larger than required during initial allocation of Disk Space when the VM is running. Previously when choosing Thin Provisioning for KVM to oVirt Importing, the Disk Size of the VM within the Storage Domain of oVirt was inflated to the Volume Size or Larger when the original KVM VM was much smaller.



Result:



Now when Importing Virtual Machines from KVM to oVirt with Thin Provisioning selected, the original Disk Size of the VM is preserved.

Feature: Added KVM Sparseness support to KVM to oVirt Virtual Machine Importing so that when Thin Provisioning is enabled, the Disk Size of the original KVM Image will be preserved after importing to oVirt. Reason: Unless the user specifically specifies pre-allocation, the Disk Size of the Virtual Machine should be no larger than required during initial allocation of Disk Space when the VM is running. Previously when choosing Thin Provisioning for KVM to oVirt Importing, the Disk Size of the VM within the Storage Domain of oVirt was inflated to the Volume Size or Larger when the original KVM VM was much smaller. Result: Now when Importing Virtual Machines from KVM to oVirt with Thin Provisioning selected, the original Disk Size of the VM is preserved. BZ 1510856 [RFE] Time sync in VM after resuming from PAUSE state

Feature:



Added optional Guest Time Synchronization to the snapshot functionality via the time_sync_snapshot_enable option and other un-pausing scenarios via the time_sync_cont_enable option for synchronizing and correcting the time on the VM after long pauses. The defaults for the option are turned off for backward compatibility.



Reason:



This becomes especially critical when there are heavy loads on the VM to ensure time stamps for example are accurate.



Result:



When the options are enabled, the VDSM shall attempt to synchronize the time either during pauses that occur via during snapshots and/or during other un-pausing functionality.

Feature: Added optional Guest Time Synchronization to the snapshot functionality via the time_sync_snapshot_enable option and other un-pausing scenarios via the time_sync_cont_enable option for synchronizing and correcting the time on the VM after long pauses. The defaults for the option are turned off for backward compatibility. Reason: This becomes especially critical when there are heavy loads on the VM to ensure time stamps for example are accurate. Result: When the options are enabled, the VDSM shall attempt to synchronize the time either during pauses that occur via during snapshots and/or during other un-pausing functionality. BZ 1451297 [RFE] Drop TLSv1 and TLSv1.1 encryption protocols support

TLSv1 and TLSv1.1 protocols are no longer secure, so they are forcefully disabled in VDSM configuration and cannot no longer be enabled within configuration.



Only TLSv1.2 and higher version of protocols are enabled, exact versions depends on underlying openssl version.

oVirt Engine

BZ 1644693 High Host CPU load for Windows 10 Guests (Update 1803) when idle

Feature: Added enlightenment support in order to reduce CPU load by enabling the hyper-visor synic and stimer states.



Reason: To improve performance when running Windows as a guest OS.



Result: Anticipated results are that CPU load will be reduced to 0-5% on Linux Virtual Machines.

Feature: Added enlightenment support in order to reduce CPU load by enabling the hyper-visor synic and stimer states. Reason: To improve performance when running Windows as a guest OS. Result: Anticipated results are that CPU load will be reduced to 0-5% on Linux Virtual Machines. BZ 1661921 ovirt-provider-ovn TLS hardening (Default use of TLSv1.2 and HIGH ciphers only)

Feature:

- internal OVN db connections are encrypted by TLS 1.2 with ‘HIGH’ chiphers in

new RHV 4.3 installations by default

- Ciphers used on ovirt-provider’s OpenStack REST API are configurable



Reason:

- bug 1459441 enables RHV to configure the encryption of OVN internal connections

- default OpenSSL config in RHEL 7 allows usage of insecure ciphers



Result:

- in RHV 4.3 default config internal OVN connections and

ovirt-provider’s OpenStack REST API uses TLS 1.2 and HIGH ciphers.

Feature: - internal OVN db connections are encrypted by TLS 1.2 with ‘HIGH’ chiphers in new RHV 4.3 installations by default - Ciphers used on ovirt-provider’s OpenStack REST API are configurable Reason: - bug 1459441 enables RHV to configure the encryption of OVN internal connections - default OpenSSL config in RHEL 7 allows usage of insecure ciphers Result: - in RHV 4.3 default config internal OVN connections and ovirt-provider’s OpenStack REST API uses TLS 1.2 and HIGH ciphers. BZ 1571371 [RFE] Allow pinning a VM (specifically high-performance) with vNUMA to more than one host

Feature: A VM with NUMA pinning enabled can now be configured to run on a set of assigned/pinned hosts (one or more).



Reason: Up till now there was a limitation that only one host (and not more than one) can be assigned to a VM, in case of NUMA nodes pinning is enabled.



Result: A VM with NUMA pinning enabled can now be configured to run on a set of assigned/pinned hosts, one or more (by selecting the “Start running on: Specific Host” in “Host” side-tab).

Each one of this hosts should have the same pinning settings so that VM can run on each and this is verified by the engine.

This change is crucial for supporting High Availability for those VMs.

Feature: A VM with NUMA pinning enabled can now be configured to run on a set of assigned/pinned hosts (one or more). Reason: Up till now there was a limitation that only one host (and not more than one) can be assigned to a VM, in case of NUMA nodes pinning is enabled. Result: A VM with NUMA pinning enabled can now be configured to run on a set of assigned/pinned hosts, one or more (by selecting the “Start running on: Specific Host” in “Host” side-tab). Each one of this hosts should have the same pinning settings so that VM can run on each and this is verified by the engine. This change is crucial for supporting High Availability for those VMs. BZ 1641125 [RFE] add a configuration policy for vGPU placement

It is now possible to set in host configuration preferred vGPU placement on physical cards. Separated placement prefers putting each vGPU on a separate physical card, consolidated placement prefers putting more vGPUs on available physical cards.

It is now possible to set in host configuration preferred vGPU placement on physical cards. Separated placement prefers putting each vGPU on a separate physical card, consolidated placement prefers putting more vGPUs on available physical cards. BZ 1539829 [RFE] Provide support for adding security groups and rules using ovirt-provider-ovn

This feature provides security group support, as described by the OpenStack Networking API.

This feature provides security group support, as described by the OpenStack Networking API. BZ 1619210 [RFE] Provide Live Migration for VMs based on “High Performance VM” Profile - automatic migrations

Feature:

This feature provides the ability to enable live migration for HP VMs (and in general to all VM types with pinning settings).



Reason:

n oVirt 4.2 we added a new “High Performance” VM profile type. This required configuration settings includes pinning the VM to a host based on the host specific configuration. Due to that pinning settings, the migration option for the HP VM type was automatically forced to be disabled.



Result:

in oVirt 4.3 we will provide the ability for live migration of HP VMs (and all other VMs with pinned configuration like NUMA pinning, CPU pinning and CPU pass-through enabled).



For more details, please refer to the feature page

Feature: This feature provides the ability to enable live migration for HP VMs (and in general to all VM types with pinning settings). Reason: n oVirt 4.2 we added a new “High Performance” VM profile type. This required configuration settings includes pinning the VM to a host based on the host specific configuration. Due to that pinning settings, the migration option for the HP VM type was automatically forced to be disabled. Result: in oVirt 4.3 we will provide the ability for live migration of HP VMs (and all other VMs with pinned configuration like NUMA pinning, CPU pinning and CPU pass-through enabled). For more details, please refer to the feature page BZ 1648190 [RHEL76] libvirt is unable to start after upgrade due to malformed UTCTIME values in cacert.pem, because properly renewed CA certificate was not passed to hosts by executing “Enroll certificate” or “Reinstall”

Internal CAs generated in the past (<= 3.5) can contain UTCTIME values without timezone indication and this is not acceptable anymore with up to date openssl and gnutls libraries.

engine-setup was already checking it proposing a remediation but the user can postpone it, making it more evident since now postponing can cause serious issues.

Internal CAs generated in the past (<= 3.5) can contain UTCTIME values without timezone indication and this is not acceptable anymore with up to date openssl and gnutls libraries. engine-setup was already checking it proposing a remediation but the user can postpone it, making it more evident since now postponing can cause serious issues. BZ 1111783 [RFE][TestOnly] Provide SCSI reservation support for virtio-scsi via rhev-guest-tools for win-8 and win-2012 guests using Direct-Lun as disks

With this release Windows clustering is supported for iSCSI based direct attached LUNs.

With this release Windows clustering is supported for iSCSI based direct attached LUNs. BZ 1598391 [RFE] - Certify OSP 14 with OVN as an external network provider on RHV 4.3

Neutron from OSP 14 configured to use OVN can be used as an external network provider on RHV 4.3 with the limitation described in bug 1655906 .

Neutron from OSP 14 configured to use OVN can be used as an external network provider on RHV 4.3 with the limitation described in bug 1655906 . BZ 1327846 [RFE] Q35: Support booting virtual machines via UEFI



BZ 1590202 [RFE] Disable Event notification popup in admin portal

This adds a feature to control toast notifications. Once 3 or more notifications are showing, “Dismiss” and “Do not disturb” buttons will appear that allow the user to silence notifications.

This adds a feature to control toast notifications. Once 3 or more notifications are showing, “Dismiss” and “Do not disturb” buttons will appear that allow the user to silence notifications. BZ 1571399 [RFE] Improve UI plugin API for adding action buttons

Feature: When adding custom action buttons (located above main or details tab grid) via UI plugin API, it’s now possible to specify the relative position of the button and whether it should be placed in the “more” menu.



Reason: Give UI plugins more control over plugin-contributed action button placement.



Result: When calling addMenuPlaceActionButton/addDetailPlaceActionButton API functions, you can now pass “index” and “moreMenu” options to customize the relative position of the button and whether it should be placed in the “more” menu. By default, the button will be placed at the end (after all existing buttons) and outside the “more” menu.

Feature: When adding custom action buttons (located above main or details tab grid) via UI plugin API, it’s now possible to specify the relative position of the button and whether it should be placed in the “more” menu. Reason: Give UI plugins more control over plugin-contributed action button placement. Result: When calling addMenuPlaceActionButton/addDetailPlaceActionButton API functions, you can now pass “index” and “moreMenu” options to customize the relative position of the button and whether it should be placed in the “more” menu. By default, the button will be placed at the end (after all existing buttons) and outside the “more” menu. BZ 1527860 [RFE] Q35: change piix3-usb controller (USB1) to qemu-xhci controller (USB3)

Feature: Adding USB qemu-xhci controller support to SPICE consoles.



Reason: For Q35 chipset support



Result: We expect when a Bios type using the Q35 chipset is chosen and usb is enabled that the USB controller shall be qemu-xhci.

Feature: Adding USB qemu-xhci controller support to SPICE consoles. Reason: For Q35 chipset support Result: We expect when a Bios type using the Q35 chipset is chosen and usb is enabled that the USB controller shall be qemu-xhci. BZ 1611889 Switch from ENI to OMP dumps network config to different file and breaks EL6 guests

Feature: Allow the user to select the cloud init protocol with which to create the network configuration for the VM



Reason: in odler versions of cloud-init, backward compatibility needs to be maintained with the ENI protocol whereas on newer cloud-init versions the Openstack-Metadata protocol is supported.



Result: engine now supports selection of the cloud-init protocol to use as part of the cloud-init parameter entry form, while creating a new VM or editing an existing one or starting a VM with Run Once.

Feature: Allow the user to select the cloud init protocol with which to create the network configuration for the VM Reason: in odler versions of cloud-init, backward compatibility needs to be maintained with the ENI protocol whereas on newer cloud-init versions the Openstack-Metadata protocol is supported. Result: engine now supports selection of the cloud-init protocol to use as part of the cloud-init parameter entry form, while creating a new VM or editing an existing one or starting a VM with Run Once. BZ 1388098 [RFE] Prevent RHV-M from restarting hosts during large outage



BZ 1630243 [RFE] Show live migration progress bar also in virtual machine tab in host page

During VM live migration, the migration progress bar is shown also in the host page on the virtual machine tab.

During VM live migration, the migration progress bar is shown also in the host page on the virtual machine tab. BZ 1559694 RFE: warn user if VM does not fit in a single numa node of the host

If a VM does not use virtual NUMA nodes, it is better if its whole memory can fit into a single NUMA node on the host. Otherwise, there may be some performance overhead.



There are two additions in this RFE:

1. New warning message is shown in the audit log, if a VM is run on a host where its memory cannot fit to a single host NUMA node.



2. A new policy unit is added to the scheduler, ‘Fit VM to single host NUMA node’. When starting a VM, this policy prefers hosts where the VM can fit to a single NUMA node. This unit is not active by default, because it can cause undesired edge cases.



For example, the policy unit would cause the following behavior when starting multiple VMs.

It the following setup:

- 9 hosts with 16 GB per NUMA node

- 1 host with 4 GB per NUMA node



When multiple VMs with 6 GB of memory are scheduled, the scheduling unit would prevent them from starting on the host with 4 GB per NUMA node. No matter how overloaded the other hosts are. It would use the last host only when all the others does not have enough free memory to run the VM.

If a VM does not use virtual NUMA nodes, it is better if its whole memory can fit into a single NUMA node on the host. Otherwise, there may be some performance overhead. There are two additions in this RFE: 1. New warning message is shown in the audit log, if a VM is run on a host where its memory cannot fit to a single host NUMA node. 2. A new policy unit is added to the scheduler, ‘Fit VM to single host NUMA node’. When starting a VM, this policy prefers hosts where the VM can fit to a single NUMA node. This unit is not active by default, because it can cause undesired edge cases. For example, the policy unit would cause the following behavior when starting multiple VMs. It the following setup: - 9 hosts with 16 GB per NUMA node - 1 host with 4 GB per NUMA node When multiple VMs with 6 GB of memory are scheduled, the scheduling unit would prevent them from starting on the host with 4 GB per NUMA node. No matter how overloaded the other hosts are. It would use the last host only when all the others does not have enough free memory to run the VM. BZ 1009608 [RFE] Limit east-west traffic of VMs with network filter

Feature:



Limit east-west traffic of VMs.



Reason:



To enable traffic only between VM and gateway.



Result:



The new filter ‘clean-traffic-gateway’ has been added to libvirt. With parameter called ‘GATEWAY_MAC’ user can specify MAC address of gateway that is allowed to communicate with the VM and vice versa. Please note that user can specify multiple ‘GATEWAY_MAC’.



There are two possible configurations of VM:



1) VM with static IP



This is recommended setup. It is also recommended setting of parameter ‘CTRL_IP_LEARNING’ to ‘none’, any other value will result in leak of initial traffic. This is caused by libvirt learning mechanism (see https://libvirt.org/formatnwfilter.html#nwfelemsRulesAdvIPAddrDetection and https://bugzilla.redhat.com/show_bug.cgi?id=1647944 for more details).



2) VM with DHCP



DHCP is working partially. It is not usable in production currently (https://bugzilla.redhat.com/show_bug.cgi?id=1651499).





The filter has general issue with ARP leak (https://bugzilla.redhat.com/show_bug.cgi?id=1651467). Peer VMs are able to see that the VM using this feature exists (in their arp table), but are not able to contact the VM, as the traffic from peers is still blocked by the filter.

Feature: Limit east-west traffic of VMs. Reason: To enable traffic only between VM and gateway. Result: The new filter ‘clean-traffic-gateway’ has been added to libvirt. With parameter called ‘GATEWAY_MAC’ user can specify MAC address of gateway that is allowed to communicate with the VM and vice versa. Please note that user can specify multiple ‘GATEWAY_MAC’. There are two possible configurations of VM: 1) VM with static IP This is recommended setup. It is also recommended setting of parameter ‘CTRL_IP_LEARNING’ to ‘none’, any other value will result in leak of initial traffic. This is caused by libvirt learning mechanism (see https://libvirt.org/formatnwfilter.html#nwfelemsRulesAdvIPAddrDetection and https://bugzilla.redhat.com/show_bug.cgi?id=1647944 for more details). 2) VM with DHCP DHCP is working partially. It is not usable in production currently (https://bugzilla.redhat.com/show_bug.cgi?id=1651499). The filter has general issue with ARP leak (https://bugzilla.redhat.com/show_bug.cgi?id=1651467). Peer VMs are able to see that the VM using this feature exists (in their arp table), but are not able to contact the VM, as the traffic from peers is still blocked by the filter. BZ 1454673 [RFE] Changes that require Virtual Machine restart: name

Feature:

When a request to rename a virtual machine arrives, change the name of the virtual machine immediately also when the QEMU process is running and is set with the previous name.



Reason:

Users typically want to see and use the new name a virtual machine is set with even when it is running.



Result:

When renaming a running virtual machine, the new name is applied immediately. In this case, the user is provided with a warning that indicates that the running instance of the virtual machine uses the previous name.

Feature: When a request to rename a virtual machine arrives, change the name of the virtual machine immediately also when the QEMU process is running and is set with the previous name. Reason: Users typically want to see and use the new name a virtual machine is set with even when it is running. Result: When renaming a running virtual machine, the new name is applied immediately. In this case, the user is provided with a warning that indicates that the running instance of the virtual machine uses the previous name. BZ 1553902 [RFE] Update UI plugin API to reflect current UI design

Starting with oVirt 4.3, the UI plugin API is updated to reflect recent web administration UI design changes.



In general, there are two types of changes:



(1) new API functions:

- addPrimaryMenuContainer & addSecondaryMenuPlace that allow plugins to add custom secondary menu items to the vertical navigation menu



(2) renaming of existing API functions:

- addMainTab => addPrimaryMenuPlace

- addSubTab => addDetailPlace

- setTabContentUrl => setPlaceContentUrl

- setTabAccessible => setPlaceAccessible

- addMainTabActionButton => addMenuPlaceActionButton

- addSubTabActionButton => addDetailPlaceActionButton



The reason for renaming API functions (2) is to stay consistent with current web administration UI design - most notably, the absence of “main” and “sub” tabs.



All existing API functions are still supported. For API functions that were renamed (2), it’s still possible to use the original ones, but doing so will yield a warning in the browser console, for example:



“addMainTab is deprecated, please use addPrimaryMenuPlace instead.”



Additionally, for functions [addPrimaryMenuPlace, addPrimaryMenuContainer, addSecondaryMenuPlace, addDetailPlace] and their deprecated equivalents, the options object no longer supports alignRight (boolean) parameter. This is because PatternFly tabs widget [1] expects all tabs to be aligned next to each other, flowing from left to right.



[1] http://www.patternfly.org/pattern-library/widgets/#tabs



For details, please consult the oVirt UI plugins feature page.

Starting with oVirt 4.3, the UI plugin API is updated to reflect recent web administration UI design changes. In general, there are two types of changes: (1) new API functions: - addPrimaryMenuContainer & addSecondaryMenuPlace that allow plugins to add custom secondary menu items to the vertical navigation menu (2) renaming of existing API functions: - addMainTab => addPrimaryMenuPlace - addSubTab => addDetailPlace - setTabContentUrl => setPlaceContentUrl - setTabAccessible => setPlaceAccessible - addMainTabActionButton => addMenuPlaceActionButton - addSubTabActionButton => addDetailPlaceActionButton The reason for renaming API functions (2) is to stay consistent with current web administration UI design - most notably, the absence of “main” and “sub” tabs. All existing API functions are still supported. For API functions that were renamed (2), it’s still possible to use the original ones, but doing so will yield a warning in the browser console, for example: “addMainTab is deprecated, please use addPrimaryMenuPlace instead.” Additionally, for functions [addPrimaryMenuPlace, addPrimaryMenuContainer, addSecondaryMenuPlace, addDetailPlace] and their deprecated equivalents, the options object no longer supports alignRight (boolean) parameter. This is because PatternFly tabs widget [1] expects all tabs to be aligned next to each other, flowing from left to right. [1] http://www.patternfly.org/pattern-library/widgets/#tabs For details, please consult the oVirt UI plugins feature page. BZ 1518697 engine-setup upgrade of postgres to pg95 env variables not stored to answer file

engine-setup now uses otopi’s new functionality to generate its answer files, which should automatically cover all future added questions without requiring specific code for handling them. The option ‘–config-append’ is compatible with both kinds of files, although the actual behavior will be somewhat different.

engine-setup now uses otopi’s new functionality to generate its answer files, which should automatically cover all future added questions without requiring specific code for handling them. The option ‘–config-append’ is compatible with both kinds of files, although the actual behavior will be somewhat different. BZ 1286219 [RFE] Disk alias of cloned VM should be Alias_ </b>

Feature:

Change the disk alias of cloned VM.



Reason:

Disk alias of cloned VM should be Alias_ .



Result:

After cloning a VM, its disks are named as

Alias_ .

BZ 1540921 [RFE] Deprecate and remove support for Conroe and Penryn CPUs

Feature:



Deprecated Conroe and Penryn CPU Types from Compatibility Version 4.3



Reason:



We no longer want to support them.





Result:



Conroe and Penryn CPU Types no longer appear for Compatibility Version 4.3 and a warning is displayed for older versions.

Feature: Deprecated Conroe and Penryn CPU Types from Compatibility Version 4.3 Reason: We no longer want to support them. Result: Conroe and Penryn CPU Types no longer appear for Compatibility Version 4.3 and a warning is displayed for older versions. BZ 968435 [RFE] Present in the UI the correlation between virtual disks in a VM and what the VM sees



BZ 1530031 [RFE] engine-backup should have defaults for most options

engine-backup now has defaults for most options, so they do not need to be supplied usually.



TODO update with the new defaults once we decide what these are.

engine-backup now has defaults for most options, so they do not need to be supplied usually. TODO update with the new defaults once we decide what these are. BZ 1602968 [RFE] Add “power off VM” to the right-click popup menu in the GUI

Feature: “Power Off VM” was missing from the context menu in the RHV-M administrator portal



Reason: This was present in previous versions, but removed as part of the new user interface.



Result: “Power Off VM” is present when a running VM is right-clicked

Feature: “Power Off VM” was missing from the context menu in the RHV-M administrator portal Reason: This was present in previous versions, but removed as part of the new user interface. Result: “Power Off VM” is present when a running VM is right-clicked BZ 1131178 [RFE] Include storage domain UUID in Storage Domain ‘General’ tab



BZ 1570077 [RFE] Add UI plugin API function to allow tab/place resource cleanup

Feature: After adding custom primary/secondary menu item or details tab via UI plugin API, it’s now possible to attach “unload” handler to perform any UI-plugin-specific cleanup once the user navigates away from the given primary/secondary menu item or details tab.



Reason: Allow UI plugins to attach “unload” handler for each plugin-contributed WebAdmin UI application place, i.e. custom primary/secondary menu item or details tab.



Result: After adding the custom application place via addPrimaryMenuPlace/addSecondaryMenuPlace/addDetailPlace API functions, you can attach “unload” handler for that place by calling api.setPlaceUnloadHandler(place, handler) function.

Feature: After adding custom primary/secondary menu item or details tab via UI plugin API, it’s now possible to attach “unload” handler to perform any UI-plugin-specific cleanup once the user navigates away from the given primary/secondary menu item or details tab. Reason: Allow UI plugins to attach “unload” handler for each plugin-contributed WebAdmin UI application place, i.e. custom primary/secondary menu item or details tab. Result: After adding the custom application place via addPrimaryMenuPlace/addSecondaryMenuPlace/addDetailPlace API functions, you can attach “unload” handler for that place by calling api.setPlaceUnloadHandler(place, handler) function. BZ 1580346 Cluster properties ‘Enable to set host/VM…’ should be set by default (and hidden?)



BZ 1454389 [RFE] add search query for cluster compatibility level override

Feature:

Added a search query to list all VMs with specific cluster compatibility override.



Result:

The new queries are:

- Vms: custom_compatibility_version = X.Y

- Vms: custom_compatibility_version != X.Y



The first lists all VMs with cluster compatibility override to version X.Y and the second lists VMs with different cluster compatibility override version or without any cluster compatibility override set.

Feature: Added a search query to list all VMs with specific cluster compatibility override. Result: The new queries are: - Vms: custom_compatibility_version = X.Y - Vms: custom_compatibility_version != X.Y The first lists all VMs with cluster compatibility override to version X.Y and the second lists VMs with different cluster compatibility override version or without any cluster compatibility override set. BZ 1408584 [RFE] Host cpu type is not found anywhere in REST API

Feature: Added the CPU Type to the REST API’s Host details.



Reason: The REST API should be consistent with the UI which does display the CPU Type.



Result: The REST API now returns the CPU Type with the rest of the Host data.

Feature: Added the CPU Type to the REST API’s Host details. Reason: The REST API should be consistent with the UI which does display the CPU Type. Result: The REST API now returns the CPU Type with the rest of the Host data. BZ 1561413 [RFE] Remove option should be grayed out for delete protected VMs

Feature: Since delete-protected VMs cannot be modified, including removal, destructive operations are now disabled.



Reason: Previously, this button was enabled, but did not perform any operations, leading to an inconsistent user experience.



Result: “Remove” is now disabled if a VM is delete protected

Feature: Since delete-protected VMs cannot be modified, including removal, destructive operations are now disabled. Reason: Previously, this button was enabled, but did not perform any operations, leading to an inconsistent user experience. Result: “Remove” is now disabled if a VM is delete protected BZ 1651255 Cannot set number of IO threads via the UI

Feature:

The number of IO threads can be set in the web UI in the new/edit VM dialog.



Reason:

Some users may need to set the number of IO threads and using web UI can be easier than REST API.

Feature: The number of IO threads can be set in the web UI in the new/edit VM dialog. Reason: Some users may need to set the number of IO threads and using web UI can be easier than REST API. BZ 1560132 [RFE] Add finer grained monitoring thresholds for memory consumption on Hypervisors to RHV

In the Administration Portal, it is possible to set a threshold for cluster level monitoring as a percentage or an absolute value, for example, 95% or 2048 MB. When usage exceeds 95% or free memory falls below 2048 MB, a “high memory usage” or “low memory available” event is logged. This reduces log clutter for clusters with large (1.5 TB) amounts of memory.

oVirt Host Dependencies

BZ 1598318 Require SCAP in ovirt-host

The openscap, openscap-utils and scap-security-guide packages have been added to oVirt Node in order to help hardening the oVirt Node deployments.

OTOPI

BZ 1316950 [RFE][CodeChange] - OTOPI should use python3 interpreter on Fedora

Feature:

OTOPI should use python3 interpreter on Fedora

Reason:



Result:

oVirt Hosted Engine Setup

BZ 1372134 [RFE] hosted-engine deployment should support IPv6

Support pure IPv6 deployments

Support pure IPv6 deployments BZ 1529063 [RFE] Allow to deploy HE with an Ansible role.

Allow the user to deploy HE with a pure ansible role.

The user should be able to deploy also on a remote host.

Allow the user to deploy HE with a pure ansible role. The user should be able to deploy also on a remote host. BZ 1209881 [RFE] remove iptables from hosted-engine.spec file to be able to deploy hosted-engine without firewall services installed

Feature: Remove iptables dependency



Reason: to be able to deploy hosted-engine without firewall services installed

oVirt Engine Data Warehouse

BZ 1614818 [RFE] Upgrade to Software Collections PostgreSQL 10

Documentation changes are being tracked in BZ1641460

oVirt Engine Metrics

BZ 1629437 Update ovirt-engine-metrics playbooks to use the linux-system-roles logging roles

Feature:

As part of replacing Fluentd wih Rsyslog we are basing the Rsyslog deployment on the linux-system-roles logging role, which is a rhel ansible role for deploying Rsyslog configuration files and service handling for multiple projects.



Reason:

This role will be maintained by RHEL and makes the Rsyslog deployment easier and more maintainable.



Result:

Rsyslog service and configurations are deployed on the oVirt engine and hosts during the ovirt metrics deployment.

oVirt Release Package

BZ 1598318 Require SCAP in ovirt-host

The openscap, openscap-utils and scap-security-guide packages have been added to oVirt Node in order to help hardening the oVirt Node deployments.

BZ 1620569 Include linux qemu-guest-agent on RHV Guest Tools iso for v2v offline conversion

Qemu Guest Agent packages for several Linux distributions have been added to ease offline installation of the guest agent

Qemu Guest Agent packages for several Linux distributions have been added to ease offline installation of the guest agent BZ 1578775 [RFE] Add qemufwcfg driver in windows guest tools

The virtio qemufwcfg driver has been added to oVirt Windows Guest Tools for Windows 10 and Windows Server 2016.

The driver doesn’t provide any functionality but prevents Windows Device Manager to display the device as unrecognized.

The virtio qemufwcfg driver has been added to oVirt Windows Guest Tools for Windows 10 and Windows Server 2016. The driver doesn’t provide any functionality but prevents Windows Device Manager to display the device as unrecognized. BZ 1578782 [RFE] Add smbus driver in windows guest tools

Feature: virtio-smbus driver installer has been added to RHV Windows Guest Tools



Reason: When a guest running Windows 2008 with Q35 bios an unknown device is listed in Device Manager being the smbus device unrecognized



Result: smbus device is now recognized.

oVirt Engine Appliance

BZ 1578835 [RFE] Add ovirt-engine-extension-aaa-ldap-setup and ovirt-engine-extension-aaa-ldap to RHV-M Image

Feature:

Add engine-extensoin-aaa-ldap to the rhvm image



Reason:

Enable LDAP provider



Result:

engine-extensoin-aaa-ldap is shipped in the rhvm image

Feature: Add engine-extensoin-aaa-ldap to the rhvm image Reason: Enable LDAP provider Result: engine-extensoin-aaa-ldap is shipped in the rhvm image BZ 1579000 [RFE] Provide RHV-M Appliance image with LVM partitioning



oVirt Node NG Image

BZ 1527120 [RFE][CodeChange] split the jenkins job and the gerrit repo if needed for nodectl tool and node-ng iso



Rebase: Bug Fixeses and Enhancementss

oVirt Engine

BZ 1441528 [RFE][Rebase] Rebase ovirt-engine on apache-sshd 2.1.0



Removed functionality

VDSM

BZ 1601873 Remove dependency on gluster-gnfs to support Gluster 4.1

In this release, gluster-gnfs is no longer available with Gluster 4.1. Users who require nfs access for gluster volumes are advised to use nfs-ganesha. Please refer to https://gluster.readthedocs.io/en/latest/Administrator%20Guide/NFS-Ganesha%20GlusterFS%20Integration/

Deprecated Functionality

oVirt Engine

BZ 1399750 [RFE] Make API v3 officially unsupported

Version 3 of the REST API has been deprecated as of RHV version 4.0. It will not be supported from RHV version 4.3, along with the ovirt-shell and version 3 of the Python SDK Guide, Ruby SDK Guide, and Java SDK Guide.

Version 3 of the REST API has been deprecated as of RHV version 4.0. It will not be supported from RHV version 4.3, along with the ovirt-shell and version 3 of the Python SDK Guide, Ruby SDK Guide, and Java SDK Guide. BZ 1627636 Drop ovirt-engine-cli dependency

The ovirt-engine-cli package uses the version 3 REST API which is deprecated and unsupported.

With this update, ovirt-engine-cli is no longer a dependency and is not installed by default.

The ovirt-engine-cli package uses the version 3 REST API which is deprecated and unsupported. With this update, ovirt-engine-cli is no longer a dependency and is not installed by default. BZ 1533086 deprecate and remove disks scan alignment feature

The “Scan Alignment” feature in the previous versions of the Administration Portal is only relevant to guest OSes that are outdated and unsupported.



The current release removes this “Scan Alignment” feature, along with historical records of disks being aligned or misaligned.

Rebase: Bug Fixeses Only

oVirt Engine

BZ 1625591 After importing KVM VM, removing the VM and re-importing, the re-importing fails

Previously, after importing and removing a Kernel-based Virtual Machine (KVM), trying to re-import the same virtual machine fails with an error that the Job ID already exists.



This update ensures that import jobs are deleted in the VDSM after importing.

Bug Fixes

VDSM

BZ 1593568 Unexpected behaviour of HA VM when host VM was running ended up Non-responsive.



BZ 1583038 [HE] Failed to deploy RHV-H on Hosted engine



BZ 1617745 startUnderlyingVm fails with exception resulting in split-brain



BZ 1575777 RHV import fails if VM has an unreachable floppy defined



BZ 1548846 Hot unplug succeeds but warnings are seen in VDSM: WARN (libvirt/events) [virt.vm] (vmId=’05361b2e-1ae3-40df-a159-cb4688b303c5’) Removed device not found in conf: scsi0-0-0-3



BZ 1297808 vdsm-4.17.17 fails make distcheck



BZ 1589612 Cannot start VM with QoS IOPS after host&engine upgrade from 4.1 to 4.2



oVirt Engine

oVirt Host Dependencies

BZ 1633975 User cannot login to RHV-H if a security profile is applied during installation



OTOPI

BZ 1381135 [FC28] otopi fails to detect firewalld if python2-firewall is not available



oVirt Hosted Engine HA

BZ 1643663 Hosted-Engine VM failed to start mixing ovirt-hosted-engine-setup from 4.1 with ovirt-hosted-engine-ha from 4.2



BZ 1636469 Removing a non-HE Host recommends user to undeploy HostedEngine on it first



oVirt Hosted Engine Setup

BZ 1662878 HE deployment fails - Failed executing ansible-playbook in get_network_interfaces



imgbased

BZ 1655003 Failed to start OpenSSH server daemon



BZ 1636028 RHVH enters emergency mode when updated to the latest version and rebooted twice



BZ 1645395 Imgbase check FAILED in redhat-virtualization-host-4.3-20181018.0.el7_6



BZ 1638606 NTP config is migrated to chrony on every upgrade



BZ 1643733 [upgrade] Post upgrade, new options are not available in virt profile



oVirt Engine Metrics

BZ 1666886 Install fluentd elasticsearch CA certificate task failed for host



oVirt Node NG Image

BZ 1634239 No SCAP security guide on Anaconda security policy page



Other

VDSM

oVirt Cockpit Plugin

BZ 1667795 Error message “Validation for this host’s FQDN failed” deploys in vm settings of Hosted engine Wizard



oVirt Setup Lib

BZ 1624599 websocket-proxy package setup fails because of missing netaddr package



oVirt Engine

oVirt Engine SDK 4 Python

BZ 1526032 [RFE] Allow uploading a pre-existing VM template image (OVA) into the environment



BZ 1622043 ovirt-engine-sdk-python use python 3.7 reserved words



oVirt Host Dependencies

BZ 1598085 ovirt-host depends on postfix when it just wants a MTA



BZ 1573186 add cockpit-machines-ovirt to RHVH hosts



OTOPI

BZ 1590723 Running otopi on fedora fails on missing cli object



BZ 1365749 [Fedora][CodeChange] otopi uses obsolete python module ‘imp’



BZ 1542529 dnf plugin is broken



oVirt Host Deploy

BZ 1588068 [CodeChange][RFE] - Package ovirt-host-deploy for python3 compatibility on Fedora



oVirt Hosted Engine HA

BZ 1579103 RHV-H 4.2.3: hosted-engine agent fails to start after upgrade due to Permission denied: ‘/var/log/ovirt-hosted-engine-ha/broker.log’ ‘/var/log/ovirt-hosted-engine-ha/agent.log’



BZ 1569593 ERROR failed to retrieve Hosted Engine HA score ‘[Errno 2] No such file or directory’ Is the Hosted Engine setup finished?



BZ 1639997 Agent fails to start with error “Failed to start monitor ping”



oVirt Hosted Engine Setup

BZ 1665467 Support host_name != host_address



BZ 1662582 Missing colon in the user dialog at the hosted-engine setup via CLI



BZ 1665419 Hosted engine wizard displays “System data could not be retrieved!” is eth0 is not available on the host



BZ 1643934 Emit a warning before running vdsm-tool restore-nets



oVirt Log Collector

BZ 1360621 log-collector should collect detailed yum/dnf history



BZ 1555449 [RFE] Reduce Archive Size by using filters message via flags unclear



BZ 1614304 spec: require the python2/3-ovirt-engine-lib instead of ovirt-engine-lib



oVirt Engine UI Extensions

BZ 1637593 [RFE] cluster upgrade dialog



imgbased

BZ 1501236 Grub2-prode failed to find the disk on LVM



oVirt Engine Data Warehouse

BZ 1639006 [CodeChange] - DWH setup should support python 3



BZ 1546486 (Fedora 27) Talend is not working properly with dom4j - 2.0.0



BZ 1507037 Race condition on starting DWH on fresh install.



oVirt Engine Metrics

BZ 1667406 Message of ovirt-engine-metrics about requiring a non existent collectd plugin during host-deploy is confusing



BZ 1664269 [RFE] Add README to the oVirt.logging role and parameterise the omelasticsearch variables



BZ 1651588 Update oVirt metrics so that host deploy will not fail due to missing Fluentd package



ovirt-engine-extension-aaa-misc

BZ 1570040 [RFE] RH Single Sign-On or OpenID Connect integration with Administration/User Portal



oVirt Release Package

BZ 1661791 [release package] Yum install of glusterfs failed because of broken repo link



BZ 1645159 change master dependencies for ovirt-web-ui rpm



BZ 1544481 Provide missing dependencies for Fedora 28



oVirt Engine Appliance

BZ 1654727 Engine Appliance image (OVA) should be arch specific, not noarch



oVirt Ansible infrastructure role

BZ 1638380 Document that ovirt.infra role needs to be executed on engine host if you want to add/modify users/groups with it



oVirt Engine

oVirt ISO Uploader

BZ 1627200 Fix ovirt-iso-uploader for python 3 compatibility



oVirt Hosted Engine Setup

BZ 1662632 Missing the option to install hosted-engine without requirements check



Contributors

112 people contributed to this release: