This bug was initially created as a copy of Bug #1963164 I am copying this bug because: It is plausible that we might hit the same issue for 16.0->16.1. It would be better if we ensure that we remove libvirt from the host as soon as possible. Description of problem: When libvirt is installed on the host along with systemd-container, systemd-container can connect to that package it tries to register the vms with systemd-machined and use systemd to configure cgroups instead of using its direct filesystem cgroup support. That causes all the vms on the host to be shutdown when the libvirt contianer is updated since none of the existing vms are registered in systemd. We should ensure that libvirt is not installed on the host during an update/upgrade so that we do not hit any of these issues if there is an update to the libvirt packages.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0986