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

[Adam Gandelman]

Public bug reported:

Similar to the EC2 instance ID issue in Bug #1061166, the
snapshot_id_mappings and volume_id_mappings tables were both introduced
in Folsom but are not populated entirely during creation, with the
deleted column ending up NULL for all rows copied during the initial
migration.

After an upgrade, queries that hope to map volume or snapshot IDs to
UUIDs fail because they query with a 'deleted=0' constraint.  Mappings
for volumes or snapshots that existed pre-upgrade cannot be found and
new entries are created, polluting the table with duplicates and skewing
the ID <-> UUIDs mapping.

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: nova (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: openstack-ubuntu-upgrade

** Also affects: nova
   Importance: Undecided
       Status: New

** Tags added: openstack-ubuntu-upgrade

-- 
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