111_general_aggregates migration fails on Postgres

Bug #1027453 reported by Dan Prince
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
High
Dan Prince

Bug Description

The 111 general aggregates migration fails to run on Postgres. The issue seems to be that the 'host' column unique constraint needs to be named explicitly on Postgres.

Dan Prince (dan-prince)
Changed in nova:
status: New → In Progress
assignee: nobody → Dan Prince (dan-prince)
importance: Undecided → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/10094

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/10094
Committed: http://github.com/openstack/nova/commit/046b3f2e0c4b6a80428aea1e69957429d23783a0
Submitter: Jenkins
Branch: master

commit 046b3f2e0c4b6a80428aea1e69957429d23783a0
Author: Dan Prince <email address hidden>
Date: Sat Jul 21 10:19:52 2012 -0400

    Updates migration 111 to work w/ Postgres.

    Updates migration 111 so that we drop the aggregate_hosts_host_key
    unique constrain by name.

    Fixes LP Bug #1027453

    Change-Id: Ibe36eace6a2d5d5a8d8d03d2cb170cbe0056320e

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → folsom-3
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: folsom-3 → 2012.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.