_update_usage_from_migrations doesn't grab instance for migration
Bug #1163622 reported by
Andrew Laski
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Andrew Laski | ||
Grizzly |
Fix Released
|
Low
|
Lance Bragstad |
Bug Description
In the resource tracker, when updating usage from migrations, a list of migrations is grabbed and then the first instance is pulled and used for all migration updates. This has the potential for invalid resource tracker updates and also for accessing system_metadata on that instance that doesn't exist.
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-grizzly |
Changed in nova: | |
importance: | Undecided → Low |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/25961
Review: https:/