Bug 2016678

Summary: RFE [16->17] Ensure that OpenStack database migrations work (Compute)
Product: Red Hat OpenStack Reporter: Jesse Pretorius <jpretori>
Component: RFEsAssignee: OSP Team <rhos-maint>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 17.0 (Wallaby)CC: alifshit, markmc
Target Milestone: betaKeywords: FutureFeature
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: 2021-11-10 17:44:35 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:
Bug Depends On:    
Bug Blocks: 2016660    

Description Jesse Pretorius 2021-10-22 16:23:18 UTC
In the OSP 16 to 17 upgrade there will be no interim containers to facilitate the database migrations like we did for 13 to 16.

The database migrations for OSP 17.x must be able to migrate directly from OSP 16.x.

Comment 1 Artom Lifshitz 2021-11-10 17:44:35 UTC
Nova has not removed any DB migrations... ever. We also have an upstream functional test that makes sure that the DB migrations apply correctly starting from a bare database. Also also, we have specifically not introduced any DB schema changes between stable/train and stable/wallaby. Because of that, we're pretty confident that this RFE's request will happen "for free". If we want to be really paranoid, can DFG:Upgrades re-raise this for the 17 -> 18 FFU? DFG:Compute doesn't expect any changes or added risk in that time frame, but it'd be good to keep awareness and visibility.