ffu: Missing Nova DB sync between O and P
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Lee Yarwood |
Bug Description
Description
===========
During a fast forward upgrade from N to Q there is no attempt to sync the main Nova DB during the O to P FFU steps. This is due to the only db sync command within the nova-api template being listed within an Ansible block that is only executed during the N to O set of FFU steps.
This results in the online DB migrations for O to P failing silently. This is however missed as the following major upgrade between P to Q, not using FFU steps, then calls for a db sync and additional online migration.
Steps to reproduce
==================
* FFU from N to Q
* Review nova-manage.log
Expected result
===============
Online migrations complete between O and P.
Actual result
=============
Online migrations fail between O and P.
Environment
===========
1. Exact version of OpenStack you are running. See the following
list for all releases: http://
N to Q FFU.
2. Which storage type did you use?
(For example: Ceph, LVM, ...)
What's the version of that?
N/A
3. Which networking type did you use?
(For example: Neutron with OpenVSwitch, ...)
N/A
Logs & Configs
==============
From the downstream bug https:/
2018-06-04 15:52:26.307 424237 ERROR oslo_db.
Fix proposed to branch: master /review. openstack. org/573740
Review: https:/