Bug 1220567 - `nova-manage db sync` randomly fails
Summary: `nova-manage db sync` randomly fails
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 6.0 (Juno)
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
: 7.0 (Kilo)
Assignee: Eoghan Glynn
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-11 21:21 UTC by Emilien Macchi
Modified: 2019-09-09 15:30 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-01 20:46:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Emilien Macchi 2015-05-11 21:21:12 UTC 
Description of problem:
Deploying OpenStack Juno 2014.2.3 by using Spinal Stack, during the deployment Nova DB sync randomly fails.
Note: I did not have this error in 2014.2.2 and I'm pretty sure my issue has bee introduced in this new release.

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

How reproducible:
Install OpenStack Juno 2014.2.3, start Nova API, Nova Conductor and run DB sync.

Steps to Reproduce:
1. Create a MySQL 'nova' database
2. Start Nova API / Nova Conductor
3. run: nova-manage db sync

Actual results:
Nova DB sync fails: http://paste.openstack.org/show/NvISe89rNuDatjccGg6O/
From 215 to 216 schema, it fails to update 'instances' table.

Expected results:
It should works.

Additional info:
During the deployment, the DB sync fails but Nova API starts.
* nova flavor-list works fine
* nova list (that contains 'instances' table) fails and you can read that in the logs: http://paste.openstack.org/show/1fa4jFWk6qUj0S3bUHJO/

Maybe this is not a bug in Nova and maybe it's something in the orchestration layer (Puppet) so please update this bug if you think this is something we have to fix in Puppet (order of startup).
Note You need to log in before you can comment on or make changes to this bug.