Volume IO usage gets reset to 0 after a reboot / crash
Bug #1169097 reported by
Michael Kerrin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Michael Kerrin | ||
Grizzly |
Fix Released
|
Low
|
Ruby Loo |
Bug Description
There is a lose of information in the volume usage after a reboot / crash of an instance.
Changed in nova: | |
assignee: | nobody → Michael Kerrin (michael-kerrin-w) |
Changed in nova: | |
status: | New → In Progress |
tags: | added: grizzly-backport-potential |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
tags: | removed: grizzly-backport-potential 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.
To reproduce:
Watch volume.usage notifications.
Perform IO on volume and see notifications increase overtime.
Reboot the instance.
volume.usage notifications have been reset to 0.
The cumulative statistics about the IO performed in step 2 is lost. Customers will be undercharged on IO requests.