076_remove_unique_constraints fails on Postgres

Bug #932154 reported by Dan Prince on 2012-02-14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Dan Prince

Bug Description

Our sqlalchemy migration 076_remove_unique_constraints script fails on Postgres.

Update the script to generically remove the unique constrains from instance_types and volume_types.

Dan Prince (dan-prince) on 2012-02-14
Changed in nova:
status: New → In Progress
assignee: nobody → Dan Prince (dan-prince)
importance: Undecided → Medium
Vish Ishaya (vishvananda) wrote :

I had a feeling this would happen, but I didn't have an install of postgres to check it on. I couldn't find a way to introspect the name of the constraint, so you may just have to add some logic to explicitly name the constraint based on db type. In fact, the odd mysql name of one of the constraints is due to a rename in one of the earlier migrations.

Dan Prince (dan-prince) wrote :
Changed in nova:
status: In Progress → Fix Committed
milestone: none → essex-4
Thierry Carrez (ttx) on 2012-02-29
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-4 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers