On Fri, Sep 25, 2020 at 1:57 PM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

oVirt Node 4.4.2 is now generally available

The oVirt project is pleased to announce the general availability of oVirt Node 4.4.2 , as of September 25th, 2020.

This release completes the oVirt 4.4.2 release published on September 17th

Thanks fir the news!

How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Due to Bug 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.2 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.2 (redeploy in case of already being on 4.4.2).

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.

What if I'm currently in 4.4.0 and want to upgrade to 4.4.2? Do I have to follow the same steps as if I were in 4.4.1 or what?

I would like to avoid going through 4.4.1 if possible.

# grep '^filter = ' /etc/lvm/lvm.conf
filter = ["a|^/dev/mapper/mpatha2$|", "r|.*|"]

Thanks,

Gianluca