Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2129445

Summary: [16.2.0 known issue][nova_libvirt tag: 16.2.0-55.1638436404] libvirt version incompatibility leaves instances in unmanageable state after minor update from RHOSP 16.2.0 to RHOSP 16.2.x
Product: Red Hat OpenStack Reporter: Artom Lifshitz <alifshit>
Component: openstack-novaAssignee: OSP DFG:Compute <osp-dfg-compute>
Status: CLOSED CURRENTRELEASE QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.2 (Train)CC: astupnik, dasmith, eglynn, jamsmith, jhakimra, jlibosva, kchamart, kgilliga, sbauza, sgordon, vromanso
Target Milestone: gaKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
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
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-06 04:56:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed: