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

Bug 2119113

Summary:	Prevent minor update from 16.2.0 if nova_libvirt 16.2.0-55.1638436404 is present
Product:	Red Hat OpenStack	Reporter:	Artom Lifshitz <alifshit>
Component:	openstack-tripleo-heat-templates	Assignee:	Mikolaj Ciecierski <mciecier>
Status:	CLOSED ERRATA	QA Contact:	Khomesh Thakre <kthakre>
Severity:	high	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	jpodivin, jpretori, jschluet, kthakre, mburns, sathlang
Target Milestone:	z5	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.6.1-2.20230309004940.f1d609a.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-26 12:16:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Artom Lifshitz 2022-08-17 14:57:45 UTC

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.

Comment 1 Sofer Athlan-Guyot 2023-02-28 13:36:35 UTC

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.

Comment 12 errata-xmlrpc 2023-04-26 12:16:45 UTC

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