[ANN] oVirt 4.3.8 is now generally available
The oVirt Project is pleased to announce the general availability of oVirt 4.3.8 as of January 27th, 2020. This update is the eighth in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] oVirt Node and Appliance have been updated including: - oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/ - Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting Vulnerability <https://www.symantec.com/security-center/vulnerabilities/writeup/111466> - Latest CentOS 7.7 updates including: - CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035571.html> - CEBA-2019:3971 CentOS 7 curl BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035558.html> - CEBA-2019:3985 CentOS 7 iproute BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035568.html> - CESA-2019:3979 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035574.html> - CEBA-2019:4106 CentOS 7 kernel BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035575.html> - CEBA-2019:3983 CentOS 7 util-linux BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035567.html> - CEBA-2019:3972 CentOS 7 sssd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035565.html> - CEBA-2019:3969 CentOS 7 samba BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035561.html> - CEBA-2019:3975 CentOS 7 libvirt BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035562.html> - CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035586.html> - CESA-2019:4190 Important CentOS 7 nss Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035590.html> - CESA-2019:4190 Important CentOS 7 nss-softokn Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035589.html> - CESA-2019:4190 Important CentOS 7 nss-util Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035587.html> - CEBA-2019:3977 CentOS 7 numactl BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035573.html> - CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035559.html> - CEBA-2019:3973 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035572.html> - CESA-2019:3976 Low CentOS 7 tcpdump Security Update <https://lists.centos.org/pipermail/centos-announce/2019-December/035570.html> - latest CentOS Virt and Storage SIG updates: - Ansible 2.9.4: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9... - Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/ Given the amount of security fixes provided by this release, upgrade is recommended as soon as practical. Additional Resources: * Read more about the oVirt 4.3.8 release highlights: http://www.ovirt.org/release/4.3.8/ * 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.3.8/ [2] http://resources.ovirt.org/pub/ovirt-4.3/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.*
Have the repositories been updated yet? Running oVIrt Node 4.3.7 with hosted engine in a cluster. Was able to successfully update the engine, bit when following the online upgrade instructions, running "Installation --> Check" on the host does not come back with any updates. Manually running an update check with 'yum update" yields the same result. Link used for updating instructions: https://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor... ________________________________________ From: Sandro Bonazzola <sbonazzo@redhat.com> Sent: Monday, January 27, 2020 7:50 AM To: users Subject: [ovirt-users] [ANN] oVirt 4.3.8 is now generally available The oVirt Project is pleased to announce the general availability of oVirt 4.3.8 as of January 27th, 2020. This update is the eighth in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but < 8) * CentOS Linux (or similar) 7.7 or later (but < 8) * oVirt Node 4.3 (available for x86_64 only) See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] oVirt Node and Appliance have been updated including: - oVirt 4.3.8: http://www.ovirt.org/release/4.3.8/ * Including fixes for CVE-2019-19336 oVirt Engine Cross Site Scripting Vulnerability<https://www.symantec.com/security-center/vulnerabilities/writeup/111466> - Latest CentOS 7.7 updates including: * CEBA-2019:3970 CentOS 7 ca-certificates BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035571.html> * CEBA-2019:3971 CentOS 7 curl BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035558.html> * CEBA-2019:3985 CentOS 7 iproute BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035568.html> * CESA-2019:3979 Important CentOS 7 kernel Security Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035574.html> * CEBA-2019:4106 CentOS 7 kernel BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035575.html> * CEBA-2019:3983 CentOS 7 util-linux BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035567.html> * CEBA-2019:3972 CentOS 7 sssd BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035565.html> * CEBA-2019:3969 CentOS 7 samba BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035561.html> * CEBA-2019:3975 CentOS 7 libvirt BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035562.html> * CEEA-2019:4161 CentOS 7 microcode_ctl Enhancement Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035586.html> * CESA-2019:4190 Important CentOS 7 nss Security Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035590.html> * CESA-2019:4190 Important CentOS 7 nss-softokn Security Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035589.html> * CESA-2019:4190 Important CentOS 7 nss-util Security Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035587.html> * CEBA-2019:3977 CentOS 7 numactl BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035573.html> * CEBA-2019:3982 CentOS 7 selinux-policy BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035559.html> * CEBA-2019:3973 CentOS 7 sos BugFix Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035572.html> * CESA-2019:3976 Low CentOS 7 tcpdump Security Update<https://lists.centos.org/pipermail/centos-announce/2019-December/035570.html> - latest CentOS Virt and Storage SIG updates: * Ansible 2.9.4: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9... * Glusterfs 6.7: https://docs.gluster.org/en/latest/release-notes/6.7/ Given the amount of security fixes provided by this release, upgrade is recommended as soon as practical. Additional Resources: * Read more about the oVirt 4.3.8 release highlights:http://www.ovirt.org/release/4.3.8/ * 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.3.8/ [2] http://resources.ovirt.org/pub/ovirt-4.3/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA<https://www.redhat.com/> sbonazzo@redhat.com<mailto:sbonazzo@redhat.com> [https://marketing-outfit-prod-images.s3-us-west-2.amazonaws.com/f5445ae0c9ddafd5b2f1836854d7416a/Logo-RedHat-Email.png]<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.
Hi, Sandro Bonazzola <sbonazzo@redhat.com> writes:
The oVirt Project is pleased to announce the general availability of oVirt 4.3.8 as of January 27th, 2020.
First, congrats on the release. Quick question. My engine is currently running 4.3.6. My host is still at 4.1.x. I was planning (this weekend) to just yum upgrade the host system to bring it up to 4.3.x. Is it okay for the host to be at 4.3.8 while the engine is still at 4.3.6? Or must I upgrade the engine to 4.3.8 first? Thanks, -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
Il giorno gio 30 gen 2020 alle ore 16:20 Derek Atkins <derek@ihtfp.com> ha scritto:
Hi,
Sandro Bonazzola <sbonazzo@redhat.com> writes:
The oVirt Project is pleased to announce the general availability of oVirt 4.3.8 as of January 27th, 2020.
First, congrats on the release.
Quick question. My engine is currently running 4.3.6. My host is still at 4.1.x. I was planning (this weekend) to just yum upgrade the host system to bring it up to 4.3.x.
Is it okay for the host to be at 4.3.8 while the engine is still at 4.3.6? Or must I upgrade the engine to 4.3.8 first?
I would recommend to upgrade engine first, but host upgrade should work fine being engine already at 4.3. I would recommend to use the engine for upgrading the hosts. It can use the cluster upgrade ansible role ( https://github.com/oVirt/ovirt-ansible-cluster-upgrade/blob/master/README.md) and save you some time.
Thanks,
-derek
-- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
-- 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. <https://mojo.redhat.com/docs/DOC-1199578>*
Once upon a time, Sandro Bonazzola <sbonazzo@redhat.com> said:
I would recommend to use the engine for upgrading the hosts. It can use the cluster upgrade ansible role ( https://github.com/oVirt/ovirt-ansible-cluster-upgrade/blob/master/README.md) and save you some time.
I guess this is the same ansible as used when clicking the "Upgrade" button on the cluster in the web UI... that doesn't seem to work for clusters with a hosted engine. It appears it won't migrate the engine to another host, so it won't upgrade the host with the engine. -- Chris Adams <cma@cmadams.net>
Hi, On Thu, January 30, 2020 10:38 am, Sandro Bonazzola wrote:
Quick question. My engine is currently running 4.3.6. My host is still at 4.1.x. I was planning (this weekend) to just yum upgrade the host system to bring it up to 4.3.x.
Is it okay for the host to be at 4.3.8 while the engine is still at 4.3.6? Or must I upgrade the engine to 4.3.8 first?
I would recommend to upgrade engine first, but host upgrade should work fine being engine already at 4.3.
Good to know. I'll see if I can find the time to upgrade the engine first.
I would recommend to use the engine for upgrading the hosts. It can use the cluster upgrade ansible role ( https://github.com/oVirt/ovirt-ansible-cluster-upgrade/blob/master/README.md) and save you some time.
Can't do that -- this is a single-host self-hosted system, so there is no where to migrate the engine. So everything needs to be done manually. At least that is my understanding. And since this is a production system I'd rather spend more time and have it work than trying something and having it fail mid-way. As I'm already planning significant downtime to move the machines to a new location and re-rack them, the additional time to "yum upgrade" shouldn't be a problem. :) -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
participants (4)
-
Chris Adams -
Derek Atkins -
Robert Webb -
Sandro Bonazzola