rename instance_info_cache instance_uuid unique constraints

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

Bug Description

In Folsom we renamed the instance_id column to instance_uuid (see Folsom migration 105 for details). This all went well except that the name of the unique constraints still reflects the old column name.

For MySQL:

instance_id should be named instance_uuid

For PostgreSQL:

instance_info_caches_instance_id_key should be named instance_info_caches_instance_uuid_key

Renaming this unique constraint will allow us to more closely match the automatic naming scheme used by python-migrate and should make naming a bit more consistent.

Dan Prince (dan-prince)
Changed in nova:
assignee: nobody → Dan Prince (dan-prince)
importance: Undecided → Medium
status: New → In Progress
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/16456

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

Reviewed: https://review.openstack.org/16456
Committed: http://github.com/openstack/nova/commit/6d65637dec129863ac4a96bb28b476f032bbff84
Submitter: Jenkins
Branch: master

commit 6d65637dec129863ac4a96bb28b476f032bbff84
Author: Dan Prince <email address hidden>
Date: Mon Nov 19 14:42:54 2012 -0500

    Rename instance_info_cache unique key constraints.

    Rename (via drop and recreate) the instance_uuid unique
    constraints on the instance_info_cache table so they reflect
    the column change name (UUID conversion) we complete in Folsom.

    Fixes LP Bug #1080837.

    Change-Id: I9dd01ebc896c1d7b51c212980e48db16bad18dec

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-2 → 2013.1
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.