Bug 2016678 - RFE [16->17] Ensure that OpenStack database migrations work (Compute)
Summary: RFE [16->17] Ensure that OpenStack database migrations work (Compute)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: beta
: ---
Assignee: OSP Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2016660
TreeView+ depends on / blocked
 
Reported: 2021-10-22 16:23 UTC by Jesse Pretorius
Modified: 2021-11-10 17:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-10 17:44:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-10530 0 None None None 2021-11-10 17:47:16 UTC
Red Hat Issue Tracker UPG-3473 0 None None None 2021-10-22 16:24:35 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.