Bug 2175921

Summary:	[18.0] Upgrade from 17.x will fail if bios setting has been stored in the DB
Product:	Red Hat OpenStack	Reporter:	Julia Kreger <jkreger>
Component:	openstack-ironic	Assignee:	Julia Kreger <jkreger>
Status:	POST ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	18.0 (Zed)	CC:	sbaker
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 Julia Kreger 2023-03-06 19:47:47 UTC

Description of problem:

Online data migrations as part of upgrades fails on Wallaby->Xena upstream, which will impact OSP18.0 upgrades.

Version-Release number of selected component (if applicable):


How reproducible:

Always re-producable if a BIOS Setting was stored

Steps to Reproduce:
1. Create a node
2. Cause to be stored/generated a BIOS Setting (for example, use redfish driver)
3. Attempt an online database migration to xena or later.

Actual results:

Upgrade fails, 'BIOSSetting' object has no attribute 'id'

Expected results:

Upgrade completes.

Additional info:

Reported upstream into OpenStack storyboard 2010632

Comment 1 Julia Kreger 2023-04-18 17:27:58 UTC

So this is actually an 18.0. 18.0 needs to know how to navigate this because the change was after wallaby (i.e. 17.1 cannot get this).

As such updating flags, and moving to post as the changes have merged.