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

Bug 1627680

Summary: [OSP12] Nova, Cinder, Ironic online data migrations not running in overcloud
Product: Red Hat OpenStack Reporter: Jiri Stransky <jstransk>
Component: openstack-tripleo-heat-templatesAssignee: Jiri Stransky <jstransk>
Status: CLOSED ERRATA QA Contact: Archit Modi <amodi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 12.0 (Pike)CC: agurenko, amcleod, augol, ccamacho, cschwede, dtantsur, jstransk, lmiccini, mburns, owalsh
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 12.0 (Pike)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-7.0.12-13.el7ost Doc Type: Bug Fix
Doc Text:
Previously, online data migrations for Nova, Cinder, and Ironic in the overcloud did not run automatically after upgrade to Red Hat OpenStack Platform 12. With this update, the `openstack overcloud upgrade converge` command triggers online data migrations when upgrading to Red Hat OpenStack Platform 12.
Story Points: ---
Clone Of: 1624899 Environment:
Last Closed: 2018-12-05 18:52:48 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: 1624899    
Bug Blocks:    

Description Jiri Stransky 2018-09-11 08:55:53 UTC
+++ This bug was initially created as a clone of Bug #1624899 +++

We're missing the code to run online data migrations of Nova, Cinder, and Ironic, after the services got containerized.

This pops up as a problem during consecutive upgrades, e.g. when upgrading 11->12->13, the Ironic DB sync will refuse to run 12->13 schema change because the online migrations have not been run on OSP 12 yet.

Comment 10 errata-xmlrpc 2018-12-05 18:52:48 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, 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-2018:3789