oVirt 4.3.1 Bugfix Release

Die Open-Source Virtualisierungslösung oVirt, wurde in der Version 4.3.1 freigegeben. oVirt selbst ist eine Alternative für VMWare und vSphere und ermöglicht das Managment von KVM Virtualisierung in Multi-Node-Umgebungen. Das neue Hauptrelease 4.3 bringt viele Verbesserungen, behebt aber auch einige Fehler.

What’s New in 4.3.1?

Enhancements

oVirt Cockpit Plugin

• BZ 1598141 [RFE] HE Node Zero should support ‚tags‘ and ’skip-tags‘ properties
  Feature: Support –tags and –skip-tags options on hosted-engine-setup
  
  Reason: Have the ability to run ansible roles with tags.
  Until now Hosted-engine run ansible playbooks with only variables.

oVirt Engine

• BZ 1467332 [RFE][Default Route] [IPv6] – Allow and enable default route network with only ipv6 boot protocol
  Feature: Support default route role on ipv6 only networks, but only for ipv6 static interface configuration.
  
  Reason: oVirt engine should support ipv6 only networks for its existing capabilities
  
  Result:
  – it is now possible to set the default route role on an ipv6 only network provided it has an ipv6 gateway.
  – for engine to correctly report the sync status of the interfaces, all interfaces should be configured with ipv6 static configuration only and an ipv6 gateway should be configured only on the network bearing the default route role.
  – ipv6 dynamic configuration is currently not supported.
  – the ipv6 gateway on the default route role network is applied as the default route for the v6 routing table on the host.
  – it is now possible to set an ipv6 gateway on non-management networks (was previously possible only on the management network).
  – if more that one ipv6 gateway is set on the interfaces of a host, engine will be in an undefined state: there will be more than one default route entry in the v6 routing table on the host which will cause the host to report that there are no v6 gateways at all meaning that the interfaces will appear as out of sync in engine.
• BZ 1671074 [RFE] Disable anonymous ciphers for engine <-> VDSM communication
  In this release, the available SSL ciphers used in communication between the Red Hat Virtualization Manager and VDSM have been limited, and now exclude weak or anonymous ciphers.
• BZ 1637015 [RFE] add option to disable toast notifications per user
  With this release, users can now silence toast notifications.
  When a toast notification appears, the user can now:
  
  Dismiss All
  or
  Do Not Disturb
  for 10 minutes
  for 1 hour
  for 1 day
  until Next Log In
• BZ 1669047 Support creating a cinderlib data-base in the engine-setup process
  In order to create and use Managed block storage domain, new database should be created for cinderlib to use.
  
  As similar to the engine database creation, this new database can be created using the engine setup process.
• BZ 1673303 Prevent setting ipv6 gw on a non default-route-role network
  Feature: Manage the ipv6 default route of a host via restricting the ipv6 default gateways on the host interfaces.
  
  Reason: Only a single ipv6 gateway should be allowed on all interfaces of a host and it should be on the network assigned the default route role of the network. Allowing to set multiple gateways causes multiple default route entries on the host routing tables which in turn might cause
  – loss of connectivity with the host on some subnets
  – host reporting no gateways at all on its interfaces
  – engine reporting networks as being out of sync
  
  Result:
  1. When the default route role is moved away from a network, its ipv6 gateway is automatically removed from the interface.
  2. After moving the default route role to a new network the user should set a static ipv6 gateway on this network.
  3. If the host and engine are not on the same subnet, engine will loose connectivity with the host on moving the default route role between networks. This is due to result (1). The user should take precautions to avoid this situation.
• BZ 1561539 [RFE] Allow adding a new host or reinstalling existing one and switching it to Maintenance without activation
  Feature:
  
  Allow adding, approving or reinstalling a host without automatically activating it afterwards.
  
  Reason:
  
  Sometimes there is performance overhead when activating a host after its addition / re-install / approval, especially when the connection to the storage-domain is problematic. Due to this it’s necessary to enable users to add / re-install /approve a host without the host being automatically activated afterwards.
  
  Result:
  
  The API will support activate=false matrix
  parameter in the URL of the request, relevant for add host, install host, approve host operations.
  
  The WebAdmin will provide „Activate Host After Install“ checkbox in add and install host dialogues, and propagate the value of the checkbox to the Engine.
  
  The default behavior remains activating the host.

Bug Fixes

VDSM

• BZ 1670370 Messages log spammed with ovs|00001|db_ctl_base|ERR|no key „odl_os_hostconfig_hostid“
  

oVirt Engine

• BZ 1658976 [Backup restore API] restore VM (created from template with thin copy) from OVF data fails – ImportVmFromConfigurationCommand fails with Error during ValidateFailure.: java.lang.NullPointerException
  
• BZ 1664342 RHV WEB-GUI sorts disk Snapshots rows alphabetically.
  
• BZ 1663616 usb forwarding does not work on VMs/templates created in 3.6 after upgrading to 4.2.7
  

Other

oVirt image transfer daemon and proxy

• BZ 1519194 ovirt-engine-rename should change ImageProxyAddress if hosted on same host as engine
  
• BZ 1670312 ovirt-imageio-daemon fails to start after reboot
  

oVirt Release Package

• BZ 1672954 Include gluster-ansible role from copr repo for CentOS and Fedora
  

oVirt Log Collector

• BZ 1641341 ovirt-log-collector python2/3 compatibility
  
• BZ 1666796 Manpage mention wrong path to logcollector.conf
  

oVirt Cockpit Plugin

• BZ 1679412 Gateway address unreachable error displays on VM settings during hosted engine deployment.
  
• BZ 1669928 Hosted engine Wizard loading failed with static IPv6 network environment.
  
• BZ 1655514 Shift from gdeploy to ansible roles
  
• BZ 1669108 Gdeploy config file in RHEL based RHHI deployment is not generated as per requirement.
  
• BZ 1673038 Hosted-engine installation wizard does not open due to network issue
  
• BZ 1679876 Validate the availability of gluster-ansible-roles before deployment
  
• BZ 1670492 The hosted-engine wizard always forces he_host_ip to the value of ansible_default_ipv4 and this could fail the deployment if the two interfaces uses different vlans
  
• BZ 1676426 Text bugs in Cockpit HE Window
  
• BZ 1679540 HC Deployment fails at FQDN validation check
  
• BZ 1679687 Hyperconverged deployment on a single host fails instantly on cockpit
  

oVirt Hosted Engine Setup

• BZ 1676928 Add flags to let the user explicitly force IPv6 or IPv4
  

oVirt Ansible hosted-engine setup role

• BZ 1654697 dmidecode ppc64
  

VDSM

• BZ 1669466 Allow setting 3 dns name servers instead of the current two
  
• BZ 1676695 „MOM not available, KSM stats will be missing“ message on random hosts, after updating to ovirt-4.3.0
  
• BZ 1658866 [scale] adding storage domain creates significant load
  
• BZ 1668727 Cinderlib- implement ManagedVolume.volume_info
  
• BZ 1610917 External VMs automatically deleted when powered down
  Vdsm takes ownership of all the VMs running on a given host. This includes any VM defined outside the System, for example by the user using command line tools.
  Vdsm also undefines the VM when they are shut down – e.g. it removes their configuration from libvirt running on the host.
  This is now done only for VMs created within the system. In other words, Vdsm now manages (stops, migrate…) externally defined VMs, but leaves them defined on shut down.
• BZ 1667978 applicability of parameter migration_max_bandwidth is not obvious
  

oVirt Host Dependencies

• BZ 1665073 On hosts add collectd write_syslog plugin dependency
  

oVirt Engine

• BZ 1676461 engine-setup should mention WA for upgrade issues (ovirt-vmconsole)
  
• BZ 1665072 On engine side add write_syslog collectd output plugin dependency
  
• BZ 1672587 VNC encryption is true on host after upgrade causing „Unsupported security types: 19“
  
• BZ 1658544 Add logging to of failed check-for-upgrade command
  
• BZ 1658249 Importing a VM from OVA that has been imported already fails and its disk status becomes illegal
  
• BZ 1672251 rename fails on KeyError ‚changed‘
  
• BZ 1607118 [IPv6] – Engine does not report out-of-sync on ipv6-enabled network
  
• BZ 1609947 Event notifications: distant position of Do Not Disturb dropdown
  
• BZ 1613402 Usage of sed -i in the dbscripts creates temporary files inside the directory
  
• BZ 1669466 Allow setting 3 dns name servers instead of the current two
  
• BZ 1509178 Wrapped provider URL in General tab of external provider
  
• BZ 1676581 [RFE] Make it possible to enable javax.net.debug in ovirt-engine-extensions-tool
  
• BZ 1660902 REST/SDK create VM snapshot with the same image id as an existing image id in that VM -> Engine Error Image IDs ${ImageId} appear
  
• BZ 1478854 Edit Host/Kernel dialog should not accept blank char as value for Kernel command line
  
• BZ 1674214 Kernel command line does not allow spaces
  
• BZ 1649285 [RFE] Re-enroll host certificates during host upgrade
  During host upgrade we do re-enroll host certificates in case the certificate is invalid.
• BZ 1667842 Automatic Migration for Affinity Labels not working
  
• BZ 1673319 [CinderLib] failed updating managed block storage – in ‚SetStorageDomainDescriptionVDS‘
  
• BZ 1429482 Difference between VV file content and data received as a response for REST api call to get VV file content.
  
• BZ 1648917 New disks cloned from template get wrong quota-id, when quota is disabled on DC
  
• BZ 1532016 [UI] – Align ‚Confirm Operation‘ checkbox in the ‚Confirm Host has been rebooted‘ dialog
  
• BZ 1662670 REST: Disk creation on a block-based domain, with provisioned size 0 is initiated and fails on vdsm
  

imgbased

• BZ 1652519 host does not meet the cluster’s minimum CPU level. Missing CPU features : spec_ctrl
• BZ 1652795 RHVH 4.3: There are warnings when running lvm commands

Quelle: https://www.ovirt.org/release/4.3.1/