[Bug 1065785] Re: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade

[OpenStack Hudson]

Reviewed:  https://review.openstack.org/14372
Committed: http://github.com/openstack/nova/commit/43bf8344488a6af1046344c255bdb2edd7450475
Submitter: Jenkins
Branch:    master

commit 43bf8344488a6af1046344c255bdb2edd7450475
Author: Adam Gandelman <adam.gandelman at canonical.com>
Date:   Thu Oct 11 18:49:54 2012 -0700

    read_deleted snapshot and volume id mappings.
    
    Since the migration that creates the volume_id_mappings and
    snapshot_id_mappings tables does not populate the 'deleted' column,
    queries to this table should not limit results to 'deleted=0'.
    Limiting to non-deleted rows results in duplicate mappings being
    created for existing instance mappings after an upgrade, and
    throws off volume and snapshot ID to UUID mapping.
    
    This is a stop-gap measure to ensure avoid serious breakage during
    an upgrade.  The NULL columns in this table are actually unused
    currently and can be populated in later grizzly migrations, if they
    end up being used.
    
    Fixes bug 1065785.
    
    Change-Id: I893c994362a203288b9984f0ede24cbb274bfcc5


** Changed in: nova
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1065785

Title:
  volume and snapshot IDs do not correctly map to UUIDs after folsom
  upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1065785/+subscriptions