Migration 015 should not use internal Glance classes
Bug #1025746 reported by
Dan Prince
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
John Bresnahan |
Bug Description
I recently made some Glance backend storage changes and was a bit surprised I had to change glance/
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.
Changed in glance: | |
importance: | Undecided → Low |
assignee: | nobody → Dan Prince (dan-prince) |
Changed in glance: | |
status: | New → Triaged |
Changed in glance: | |
milestone: | none → folsom-rc1 |
Changed in glance: | |
assignee: | Dan Prince (dan-prince) → nobody |
milestone: | folsom-rc1 → none |
Changed in glance: | |
milestone: | grizzly-rc1 → havana-1 |
Changed in glance: | |
assignee: | nobody → John Bresnahan (jbresnah) |
Changed in glance: | |
milestone: | havana-1 → grizzly-rc1 |
tags: | added: grizzly-rc-potential |
Changed in glance: | |
milestone: | grizzly-rc1 → none |
tags: |
added: grizzly-backport-potential removed: grizzly-rc-potential |
tags: |
added: grizzly-rc-potential removed: grizzly-backport-potential |
Changed in glance: | |
importance: | High → Medium |
tags: |
added: grizzly-backport-potential removed: grizzly-rc-potential |
Changed in glance: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | havana-1 → 2013.2 |
tags: | removed: grizzly-backport-potential |
To post a comment you must log in.
This also affects 017_quote_ encrypted_ swift_credentia ls.py
This is a big deal because the StoreLocation code could easily change, and thus break the expectations being placed on it in migrations. We also don't want to have to prevent beneficial changes in StoreLocation just because they might break migrations.