Description of problem: If a minor update is initiated with container nova_libvirt 16.2.0-55.1638436404 present, instances will get stuck in NOSTATE. This is captured in BZ 2109350. This current Bugzilla is *not* to fix that (we already have a KCS to get out of the NOSTATE - https://access.redhat.com/solutions/6969430), but rather to prevent customer from getting into NOSTATE to begin with, and to ideally block the minor update until they've followed manual steps install an "updatable" libvirt version. Version-Release number of selected component (if applicable): nova_libvirt 16.2.0-55.1638436404 How reproducible: 100% Steps to Reproduce: 1. Start minor update Actual results: Instances in NOSTATE Expected results: Minor update is blocked until correct version of libvirt container is deployed. Additional info: The manual steps to actually achieve the above expected results are yet TBD, but will looks similar to the steps outlined in the existing KCS.
Hi, currently reviewing the best course of action for this one. Two leads are explored: - a validation that would fail if the starting version is the aforementioned one and point to a kcs; - a error at step 0 in the same vein than the rhel version checks.
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.2.5 (Train) 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-2023:1763