oVirt 4.4.6 Fourth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Fourth Release Candidate for testing, as of April 15th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. Rebase on CentOS Stream Starting with oVirt 4.4.6 RC4 both oVirt Node and oVirt Engine Appliance are based on CentOS Stream. You can still install oVirt 4.4.6 on Red Hat Enterprise Linux, CentOS Linux or equivalent. Please note that when 4.4.6 will be released as generally available, existing oVirt Nodes updating to 4.4.6 will automatically be based on CentOS Stream. Help testing this release candidate will help ensuring a smooth experience for your main installation. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.6 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.6 (redeploy in case of already being on 4.4.6). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not be used in production. Known issues: - Bug 1946095 <https://bugzilla.redhat.com/show_bug.cgi?id=1946095> - "No valid network interface has been found" when starting HE deployment via cockpit - For testing purposes you can use the command line <https://ovirt.org/documentation/installing_ovirt_as_a_self-hosted_engine_using_the_command_line/> Installation instructions For installation instructions and additional information please refer to: https://ovirt.org/documentation/ This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.3 or newer * CentOS 8 Stream * CentOS Linux (or similar) 8.3 or newer This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS 8 Stream * CentOS Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS 8 Stream (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available based on CentOS 8 Stream - oVirt Node NG is already available based on CentOS 8 Stream Additional Resources: * Read more about the oVirt 4.4.6 release highlights: http://www.ovirt.org/release/4.4.6/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.6/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*