yahoo-eng-team team mailing list archive

[Mark Washenberger <1012820@xxxxxxxxxxxxxxxxxx>]

** Changed in: glance
       Status: In Progress => Won't Fix

** Changed in: glance/essex
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1012820

Title:
  Diablo->Essex migration breaks Nova image_ref

Status in OpenStack Image Registry and Delivery Service (Glance):
  Won't Fix
Status in Glance essex series:
  Won't Fix

Bug description:
  The upgrade process from integer ids to uuids in Glance Essex breaks
  the image_ref attribute of instances in Nova. So, for example,
  snapshotting will be impossibile (see
  https://bugs.launchpad.net/nova/+bug/1012814).

  Possible solutions.
  1. Preserve old ids like keystone preserves them. It assumes patching glance (that performs uuid validation on given ids) and nova (it performs such an image id validation, too).
  2. Update nova ids. Seems to be painful because one migration script should update both databases. However, we can just pad old ids to uuids (46 -> 00000000-0000-0000-0000-000000000046 - looks like IUnknown, but contains 0000, not C000).

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