- Announce - oVirt List Archives

[ANN] Async oVirt Node release for oVirt 4.4.6
by Sandro Bonazzola 11 May '21

11 May '21

On May 10th 2021 the oVirt project released an async update of oVirt Node (4.4.6.1) Changes: - Updated Advanced Virtualization packages - Updated ovn2.11 and openvswitch2.11 - Updated ansible 2.9.21 ( https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… ) - Update libssh (fixes CVE-2020-16135) Full diff list: --- ovirt-node-ng-image-4.4.6.manifest-rpm 2021-05-04 17:02:01.839123874 +0200 +++ ovirt-node-ng-image-4.4.6.1.manifest-rpm 2021-05-11 08:39:44.714649170 +0200 @@ -24 +24 @@ -ansible-2.9.20-2.el8.noarch +ansible-2.9.21-2.el8.noarch @@ -89 +89 @@ -corosynclib-3.1.0-4.el8.0.1.x86_64 +corosynclib-3.1.0-5.el8.x86_64 @@ -100 +100 @@ -cups-libs-2.2.6-38.el8.x86_64 +cups-libs-2.2.6-39.el8.x86_64 @@ -130,5 +130,5 @@ -dracut-049-135.git20210121.el8.x86_64 -dracut-config-generic-049-135.git20210121.el8.x86_64 -dracut-live-049-135.git20210121.el8.x86_64 -dracut-network-049-135.git20210121.el8.x86_64 -dracut-squash-049-135.git20210121.el8.x86_64 +dracut-049-136.git20210426.el8.x86_64 +dracut-config-generic-049-136.git20210426.el8.x86_64 +dracut-live-049-136.git20210426.el8.x86_64 +dracut-network-049-136.git20210426.el8.x86_64 +dracut-squash-049-136.git20210426.el8.x86_64 @@ -148,36 +148,36 @@ -fence-agents-all-4.2.1-67.el8.x86_64 -fence-agents-amt-ws-4.2.1-67.el8.noarch -fence-agents-apc-4.2.1-67.el8.noarch -fence-agents-apc-snmp-4.2.1-67.el8.noarch -fence-agents-bladecenter-4.2.1-67.el8.noarch -fence-agents-brocade-4.2.1-67.el8.noarch -fence-agents-cisco-mds-4.2.1-67.el8.noarch -fence-agents-cisco-ucs-4.2.1-67.el8.noarch -fence-agents-common-4.2.1-67.el8.noarch -fence-agents-compute-4.2.1-67.el8.noarch -fence-agents-drac5-4.2.1-67.el8.noarch -fence-agents-eaton-snmp-4.2.1-67.el8.noarch -fence-agents-emerson-4.2.1-67.el8.noarch -fence-agents-eps-4.2.1-67.el8.noarch -fence-agents-heuristics-ping-4.2.1-67.el8.noarch -fence-agents-hpblade-4.2.1-67.el8.noarch -fence-agents-ibmblade-4.2.1-67.el8.noarch -fence-agents-ifmib-4.2.1-67.el8.noarch -fence-agents-ilo-moonshot-4.2.1-67.el8.noarch -fence-agents-ilo-mp-4.2.1-67.el8.noarch -fence-agents-ilo-ssh-4.2.1-67.el8.noarch -fence-agents-ilo2-4.2.1-67.el8.noarch -fence-agents-intelmodular-4.2.1-67.el8.noarch -fence-agents-ipdu-4.2.1-67.el8.noarch -fence-agents-ipmilan-4.2.1-67.el8.noarch -fence-agents-kdump-4.2.1-67.el8.x86_64 -fence-agents-mpath-4.2.1-67.el8.noarch -fence-agents-redfish-4.2.1-67.el8.x86_64 -fence-agents-rhevm-4.2.1-67.el8.noarch -fence-agents-rsa-4.2.1-67.el8.noarch -fence-agents-rsb-4.2.1-67.el8.noarch -fence-agents-sbd-4.2.1-67.el8.noarch -fence-agents-scsi-4.2.1-67.el8.noarch -fence-agents-vmware-rest-4.2.1-67.el8.noarch -fence-agents-vmware-soap-4.2.1-67.el8.noarch -fence-agents-wti-4.2.1-67.el8.noarch +fence-agents-all-4.2.1-68.el8.x86_64 +fence-agents-amt-ws-4.2.1-68.el8.noarch +fence-agents-apc-4.2.1-68.el8.noarch +fence-agents-apc-snmp-4.2.1-68.el8.noarch +fence-agents-bladecenter-4.2.1-68.el8.noarch +fence-agents-brocade-4.2.1-68.el8.noarch +fence-agents-cisco-mds-4.2.1-68.el8.noarch +fence-agents-cisco-ucs-4.2.1-68.el8.noarch +fence-agents-common-4.2.1-68.el8.noarch +fence-agents-compute-4.2.1-68.el8.noarch +fence-agents-drac5-4.2.1-68.el8.noarch +fence-agents-eaton-snmp-4.2.1-68.el8.noarch +fence-agents-emerson-4.2.1-68.el8.noarch +fence-agents-eps-4.2.1-68.el8.noarch +fence-agents-heuristics-ping-4.2.1-68.el8.noarch +fence-agents-hpblade-4.2.1-68.el8.noarch +fence-agents-ibmblade-4.2.1-68.el8.noarch +fence-agents-ifmib-4.2.1-68.el8.noarch +fence-agents-ilo-moonshot-4.2.1-68.el8.noarch +fence-agents-ilo-mp-4.2.1-68.el8.noarch +fence-agents-ilo-ssh-4.2.1-68.el8.noarch +fence-agents-ilo2-4.2.1-68.el8.noarch +fence-agents-intelmodular-4.2.1-68.el8.noarch +fence-agents-ipdu-4.2.1-68.el8.noarch +fence-agents-ipmilan-4.2.1-68.el8.noarch +fence-agents-kdump-4.2.1-68.el8.x86_64 +fence-agents-mpath-4.2.1-68.el8.noarch +fence-agents-redfish-4.2.1-68.el8.x86_64 +fence-agents-rhevm-4.2.1-68.el8.noarch +fence-agents-rsa-4.2.1-68.el8.noarch +fence-agents-rsb-4.2.1-68.el8.noarch +fence-agents-sbd-4.2.1-68.el8.noarch +fence-agents-scsi-4.2.1-68.el8.noarch +fence-agents-vmware-rest-4.2.1-68.el8.noarch +fence-agents-vmware-soap-4.2.1-68.el8.noarch +fence-agents-wti-4.2.1-68.el8.noarch @@ -187 +187 @@ -filesystem-3.8-4.el8.x86_64 +filesystem-3.8-3.el8.x86_64 @@ -193 +193 @@ -freetype-2.9.1-5.el8.x86_64 +freetype-2.9.1-4.el8_3.1.x86_64 @@ -199 +199 @@ -fwupd-1.5.5-3.el8.x86_64 +fwupd-1.5.9-1.el8.x86_64 @@ -210 +210 @@ -glib2-2.56.4-10.el8.x86_64 +glib2-2.56.4-11.el8.x86_64 @@ -269,2 +269,2 @@ -iproute-5.9.0-4.el8.x86_64 -iproute-tc-5.9.0-4.el8.x86_64 +iproute-5.12.0-0.el8.x86_64 +iproute-tc-5.12.0-0.el8.x86_64 @@ -317,2 +317,2 @@ -krb5-libs-1.18.2-9.el8.x86_64 -krb5-workstation-1.18.2-9.el8.x86_64 +krb5-libs-1.18.2-10.el8.x86_64 +krb5-workstation-1.18.2-10.el8.x86_64 @@ -381 +381 @@ -libgcc-8.4.1-1.el8.x86_64 +libgcc-8.4.1-2.1.el8.x86_64 @@ -393 +393 @@ -libgomp-8.4.1-1.el8.x86_64 +libgomp-8.4.1-2.1.el8.x86_64 @@ -409 +409 @@ -libkadm5-1.18.2-9.el8.x86_64 +libkadm5-1.18.2-10.el8.x86_64 @@ -469,2 +469,2 @@ -libssh-0.9.4-2.el8.x86_64 -libssh-config-0.9.4-2.el8.noarch +libssh-0.9.4-3.el8.x86_64 +libssh-config-0.9.4-3.el8.noarch @@ -476 +476 @@ -libstdc++-8.4.1-1.el8.x86_64 +libstdc++-8.4.1-2.1.el8.x86_64 @@ -498,26 +498,26 @@ -libvirt-7.0.0-9.el8s.x86_64 -libvirt-admin-7.0.0-9.el8s.x86_64 -libvirt-bash-completion-7.0.0-9.el8s.x86_64 -libvirt-client-7.0.0-9.el8s.x86_64 -libvirt-daemon-7.0.0-9.el8s.x86_64 -libvirt-daemon-config-network-7.0.0-9.el8s.x86_64 -libvirt-daemon-config-nwfilter-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-interface-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-network-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-nodedev-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-nwfilter-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-qemu-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-secret-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-core-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-disk-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-gluster-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-iscsi-direct-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-logical-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-mpath-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-rbd-7.0.0-9.el8s.x86_64 -libvirt-daemon-driver-storage-scsi-7.0.0-9.el8s.x86_64 -libvirt-daemon-kvm-7.0.0-9.el8s.x86_64 -libvirt-libs-7.0.0-9.el8s.x86_64 -libvirt-lock-sanlock-7.0.0-9.el8s.x86_64 +libvirt-7.0.0-14.el8s.x86_64 +libvirt-admin-7.0.0-14.el8s.x86_64 +libvirt-bash-completion-7.0.0-14.el8s.x86_64 +libvirt-client-7.0.0-14.el8s.x86_64 +libvirt-daemon-7.0.0-14.el8s.x86_64 +libvirt-daemon-config-network-7.0.0-14.el8s.x86_64 +libvirt-daemon-config-nwfilter-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-interface-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-network-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-nodedev-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-nwfilter-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-qemu-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-secret-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-core-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-disk-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-gluster-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-iscsi-direct-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-logical-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-mpath-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-rbd-7.0.0-14.el8s.x86_64 +libvirt-daemon-driver-storage-scsi-7.0.0-14.el8s.x86_64 +libvirt-daemon-kvm-7.0.0-14.el8s.x86_64 +libvirt-libs-7.0.0-14.el8s.x86_64 +libvirt-lock-sanlock-7.0.0-14.el8s.x86_64 @@ -533 +533,2 @@ -libxcrypt-4.1.1-5.el8.x86_64 +libxcrypt-4.1.1-6.el8.x86_64 +libxkbcommon-0.9.1-1.el8.x86_64 @@ -618,2 +619,2 @@ -openscap-1.3.4-5.el8.x86_64 -openscap-scanner-1.3.4-5.el8.x86_64 +openscap-1.3.5-2.el8.x86_64 +openscap-scanner-1.3.5-2.el8.x86_64 @@ -626 +627 @@ -openvswitch2.11-2.11.0-50.el8.x86_64 +openvswitch2.11-2.11.3-87.el8s.x86_64 @@ -642 +643 @@ -ovirt-node-ng-image-update-placeholder-4.4.6-1.el8.noarch +ovirt-node-ng-image-update-placeholder-4.4.6.1-1.el8.noarch @@ -650,2 +651,2 @@ -ovirt-release-host-node-4.4.6-1.el8.noarch -ovirt-release44-4.4.6-1.el8.noarch +ovirt-release-host-node-4.4.6.1-1.el8.noarch +ovirt-release44-4.4.6.1-1.el8.noarch @@ -654,2 +655,2 @@ -ovn2.11-2.11.1-39.el8.x86_64 -ovn2.11-host-2.11.1-39.el8.x86_64 +ovn2.11-2.11.1-57.el8s.x86_64 +ovn2.11-host-2.11.1-57.el8s.x86_64 @@ -788 +789 @@ -python3-openvswitch2.11-2.11.0-50.el8.x86_64 +python3-openvswitch2.11-2.11.3-87.el8s.x86_64 @@ -828 +829 @@ -python3-subscription-manager-rhsm-1.28.13-2.el8.x86_64 +python3-subscription-manager-rhsm-1.28.16-1.el8.x86_64 @@ -830 +831 @@ -python3-syspurpose-1.28.13-2.el8.x86_64 +python3-syspurpose-1.28.16-1.el8.x86_64 @@ -836,12 +837,14 @@ -qemu-guest-agent-5.2.0-11.el8s.x86_64 -qemu-img-5.2.0-11.el8s.x86_64 -qemu-kvm-5.2.0-11.el8s.x86_64 -qemu-kvm-block-curl-5.2.0-11.el8s.x86_64 -qemu-kvm-block-gluster-5.2.0-11.el8s.x86_64 -qemu-kvm-block-iscsi-5.2.0-11.el8s.x86_64 -qemu-kvm-block-rbd-5.2.0-11.el8s.x86_64 -qemu-kvm-block-ssh-5.2.0-11.el8s.x86_64 -qemu-kvm-common-5.2.0-11.el8s.x86_64 -qemu-kvm-core-5.2.0-11.el8s.x86_64 -quota-4.04-13.el8.x86_64 -quota-nls-4.04-13.el8.noarch +qemu-guest-agent-5.2.0-16.el8s.x86_64 +qemu-img-5.2.0-16.el8s.x86_64 +qemu-kvm-5.2.0-16.el8s.x86_64 +qemu-kvm-block-curl-5.2.0-16.el8s.x86_64 +qemu-kvm-block-gluster-5.2.0-16.el8s.x86_64 +qemu-kvm-block-iscsi-5.2.0-16.el8s.x86_64 +qemu-kvm-block-rbd-5.2.0-16.el8s.x86_64 +qemu-kvm-block-ssh-5.2.0-16.el8s.x86_64 +qemu-kvm-common-5.2.0-16.el8s.x86_64 +qemu-kvm-core-5.2.0-16.el8s.x86_64 +qemu-kvm-ui-opengl-5.2.0-16.el8s.x86_64 +qemu-kvm-ui-spice-5.2.0-16.el8s.x86_64 +quota-4.04-14.el8.x86_64 +quota-nls-4.04-14.el8.noarch @@ -889 +892 @@ -sos-4.0-11.el8.noarch +sos-4.1-1.el8.noarch @@ -903 +906 @@ -subscription-manager-rhsm-certificates-1.28.13-2.el8.x86_64 +subscription-manager-rhsm-certificates-1.28.16-1.el8.x86_64 @@ -960,0 +964 @@ +xkeyboard-config-2.28-1.el8.noarch @@ -963,0 +968,2 @@ +xmlsec1-1.2.25-4.el8.x86_64 +xmlsec1-openssl-1.2.25-4.el8.x86_64 -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)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.*

1 0

[ANN] Async release for oVirt 4.4.6
by Sandro Bonazzola 07 May '21

07 May '21

on May 7th 2021 the oVirt project released an async update to the following packages: - ovirt-engine-extension-aaa-ldap-1.4.3 - ovirt-engine-4.4.6.7 Fixing the following bugs: - Bug 1896779 <https://bugzilla.redhat.com/show_bug.cgi?id=1896779> - Unable to access LDAP server using IPv6 when both engine and LDAP are configured with IPv6 interfaces only, but DNS records for LDAP contains also IPv4 address - Bug 1940138 <https://bugzilla.redhat.com/show_bug.cgi?id=1940138> - AAA - IPV6 detection needs to be disabled for LDAP hosts to be recognized - Bug 1941541 <https://bugzilla.redhat.com/show_bug.cgi?id=1941541> - ldap setup fails to login with connection error when use dns is specified - Bug 1950209 <https://bugzilla.redhat.com/show_bug.cgi?id=1950209> - Leaf images used by the VM is deleted by the engine during snapshot merge - Bug 1957595 <https://bugzilla.redhat.com/show_bug.cgi?id=1957595> - Failed to import VM from KVM - Bug 1956677 <https://bugzilla.redhat.com/show_bug.cgi?id=1956677> - Snapshot merge fails with null pointer exception. We are planning an oVirt Node async once libvirt fix for Bug 1953577 <https://bugzilla.redhat.com/show_bug.cgi?id=1953577> will be available from CentOS Virtualization SIG. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)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.*

1 0

oVirt 4.4.6 is now generally available
by Lev Veyde 04 May '21

04 May '21

The oVirt project is excited to announce the general availability of oVirt 4.4.6 , as of May 4th, 2021. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJ… ) Rebase on CentOS Stream Starting with oVirt 4.4.6 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 8.3, CentOS Linux 8.3 or equivalent but in order to use cluster level 4.6 you’ll have to wait for 8.4 to be available. Please note that existing oVirt Nodes updating to 4.4.6 will automatically be based on CentOS Stream. 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>. What’s new in oVirt 4.4.6 Release? This update is the sixth in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.3 - CentOS Linux (or similar) 8.3 - oVirt Node NG (based on CentOS Stream 8) - CentOS Stream oVirt Node and Appliance have been updated, including: - oVirt 4.4.6: https://www.ovirt.org/release/4.4.6/ - CentOS Stream 8 - Ansible 2.9.20: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.… - Advanced Virtualization 8.4 See the release notes [1] for installation instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for CentOS Stream 8 - oVirt Node NG is already available for CentOS Stream 8 Additional resources: - Read more about the oVirt 4.4.6 release highlights: https://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: https://blogs.ovirt.org/ [1] https://www.ovirt.org/release/4.4.6/ [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[ANN] oVirt 4.4.6 Sixth Release Candidate is now available for testing
by Lev Veyde 29 Apr '21

29 Apr '21

oVirt 4.4.6 Sixth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Sixth Release Candidate for testing, as of April 29th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. 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. 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 Linux (or similar) 8.3 or newer * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (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 Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 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/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[ANN] oVirt 4.4.6 Fifth Release Candidate is now available for testing
by Lev Veyde 22 Apr '21

22 Apr '21

oVirt 4.4.6 Fifth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Fifth Release Candidate for testing, as of April 22nd, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. 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. 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 Linux (or similar) 8.3 or newer * CentOS Stream 8 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.3 or newer * CentOS Linux (or similar) 8.3 or newer * CentOS Stream 8 * oVirt Node 4.4 based on CentOS Stream 8 (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 Stream 8 - oVirt Node NG is already available based on CentOS Stream 8 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/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[ANN] oVirt 4.4.6 Fourth Release Candidate is now available for testing
by Sandro Bonazzola 15 Apr '21

15 Apr '21

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_us…> 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(a)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.*

1 0

[ANN] oVirt 4.4.6 Third Release Candidate is now available for testing
by Lev Veyde 08 Apr '21

08 Apr '21

oVirt 4.4.6 Third Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Third Release Candidate for testing, as of April 8th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. 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. 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 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 Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.6 Node and Appliance on CentOS Linux. 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/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[ANN] oVirt 4.4.6 Second Release Candidate is now available for testing
by Lev Veyde 01 Apr '21

01 Apr '21

oVirt 4.4.6 Second Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 Second Release Candidate for testing, as of April 1st, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. 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. 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 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 Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.6 Node and Appliance on CentOS Linux. 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/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[ANN] oVirt 4.4.6 First Release Candidate is now available for testing
by Lev Veyde 25 Mar '21

25 Mar '21

oVirt 4.4.6 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.6 First Release Candidate for testing, as of March 25th, 2021. This update is the sixth in a series of stabilization updates to the 4.4 series. 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. 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 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 Linux (or similar) 8.3 or newer * oVirt Node 4.4 based on CentOS Linux 8.3 (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 for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 - We found a few issues while testing on CentOS Stream so we are still basing oVirt 4.4.6 Node and Appliance on CentOS Linux. 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/ -- Lev Veyde Senior Software Engineer, RHCE | RHCVA | MCITP Red Hat Israel <https://www.redhat.com> lev(a)redhat.com | lveyde(a)redhat.com <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0

[ANN] Async release for oVirt 4.4.5
by Sandro Bonazzola 24 Mar '21

24 Mar '21

On March 23rd 2021 the oVirt project released an async update to the following packages: - ovirt-ansible-collection-1.4.1 - vdsm-4.40.50.9 - ovirt-engine-4.4.5.11 - ovirt-release44-4.4.5.1 - ovirt-engine-appliance-4.4-20210323171213.1 - oVirt Node is still building, will follow tomorrow. Fixing the following bugs: - Bug 1940438 <https://bugzilla.redhat.com/show_bug.cgi?id=1940438> - Revoking a token using ovirt_auth module fails hosted_engine_setup ansible role - Bug 1941311 <https://bugzilla.redhat.com/show_bug.cgi?id=1941311> - Live merge after extend disk fails - 'Vm' object has no attribute 'refreshDriveVolume' - Bug 1940448 <https://bugzilla.redhat.com/show_bug.cgi?id=1940448> - Upgrade to 4.4.5 fails schema upgrade if user_profiles table contains duplicate entries -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)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.*

1 1