Do not update from RHOSP 16.2.0 to 16.2.2 or 16.2.3 until you evaluate your risk of serious impact from a libvirt version incompatibility. To complete this evaluation, perform the following step: + . Check the libvirt package in the `nova_libvirt` container in all compute nodes: + ---- $ sudo podman exec nova_libvirt rpm -q libvirt ---- + If the libvirt version is 7.0, the update path IS NOT affected by the bug. You can perform the update. + If the libvirt version is 7.6, the update path is affected by the bug. Your update is at risk. + + If you learn that your update is at risk from the libvirt incompatibility, choose one of these options: * Wait: Update directly to RHOSP 16.2.4 when it is released. It will include a fix for the incompatibility issue. This is the preferred option if you can postpone the update. * Hot fix: Contact your Red Hat support representative to explore whether your environment is compatible for a hot fix patch that resolves the issue. Use this option if there is a strong business need for an immediate update. + If you already performed the update with the version incompatibility, see the KCS article [2] for guidance on fixing the problem. [1] Article helps you verify if your update path is at risk (same step as above). Also includes steps you can perform to update to 16.2.1, 16.2.2, or 16.2.3 if you choose the second option and receive hot fixes. + https://access.redhat.com/solutions/6972451 + [2] Article helps you fix your deployment if you already completed an update to 16.2.1, 16.2.2, or 16.2.3 and your deployment is affected by the incompatibility. https://access.redhat.com/solutions/6969430