[openstack-dev] [Nova] Grizzly -> Havanna db migration bug/1245502 still biting me?

Joshua Hesketh joshua.hesketh at RACKSPACE.COM
Thu Jan 2 12:39:29 UTC 2014


Just FYI this backport has now merged. Hopefully this will mean it'll get you past now.

Cheers,
Josh
________________________________________
From: Joshua Hesketh [joshua.hesketh at RACKSPACE.COM]
Sent: Wednesday, January 01, 2014 11:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova] Grizzly -> Havanna db migration bug/1245502 still biting me?

Hi Jon,

The issue here is that the backport into Havana hasn't been merged yet: https://review.openstack.org/#/c/56149/

I apologise for the delay, It has been in review for a long time.

If there are some stable maintainers that are able to take a look that would be really appreciated.

Cheers,
Josh
________________________________________
From: Jonathan Proulx [jon at jonproulx.com]
Sent: Tuesday, December 31, 2013 5:25 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Nova] Grizzly -> Havanna db migration bug/1245502     still biting me?

Hi All,

I'm mid upgrade between Grizzly and Havana and seem to still be having
issues with https://bugs.launchpad.net/nova/+bug/1245502

I grabbed the patched version of 185_rename_unique_constraints.py but
that migration still keeps failing with many issues trying to drop
nonexistant indexes and add preexisting indexes.

for example:
CRITICAL nova [-] (OperationalError) (1553, "Cannot drop index
'uniq_instance_type_id_x_project_id_x_deleted': needed in a foreign
key constraint") 'ALTER TABLE instance_type_projects DROP INDEX
uniq_instance_type_id_x_project_id_x_deleted' ()


I'm on Ubuntu 12.04 having originally installed Essex and
progressively upgraded using cloud archive packages since.

# nova-manage  db version
184

a dump of my nova database schema as it currently stands is at:
https://gist.github.com/jon-proulx/79a77e8b771f90847ae9

The bug is marked "fix released", but one of the last comments request
schemata from affected systems so not sure if replying to the bug is
appropriate or if this should be a new bug.

-Jon

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list