volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade
Bug #1065785 reported by
Adam Gandelman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Adam Gandelman | ||
Folsom |
Fix Released
|
High
|
Adam Gandelman | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Similar to the EC2 instance ID issue in Bug #1061166, the snapshot_
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.
Related branches
CVE References
tags: | added: openstack-ubuntu-upgrade |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/14372
Review: https:/