076_remove_unique_constraints fails on Postgres
Bug #932154 reported by
Dan Prince
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Dan Prince | ||
Bug Description
Our sqlalchemy migration 076_remove_
Update the script to generically remove the unique constrains from instance_types and volume_types.
| Changed in nova: | |
| status: | New → In Progress |
| assignee: | nobody → Dan Prince (dan-prince) |
| importance: | Undecided → Medium |
Revision history for this message
| Vish Ishaya (vishvananda) wrote | #1 |
Revision history for this message
| Dan Prince (dan-prince) wrote | #2 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| milestone: | none → essex-4 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | essex-4 → 2012.1 |
To post a comment you must log in.
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.