yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1025746] Re: Migration 015 should not use internal Glance classes

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Wed, 29 May 2013 08:53:26 -0000
Reply-to: Bug 1025746 <1025746@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: glance
       Status: Fix Committed => Fix Released

** Changed in: glance
    Milestone: None => havana-1

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

Title:
  Migration 015 should not use internal Glance classes

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Released

Bug description:
  I recently made some Glance backend storage changes and was a bit
  surprised I had to change
  glance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.py
  (a database migration) in order for tests to pass.

  It would be best if Glance migrations did not rely on internal Glance
  classes when performing data migrations. If we need access to a
  backend storage class we should implement an inline version in this
  migration.

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