Resize Usage Events should use DB timestamp
Bug #1236620 reported by
Justin Hopper
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Critical
|
Justin Hopper |
Bug Description
In order to keep accurate record of when the instance or volume was resized, we should use the same timestamp for both the database record and for the usage event. Currently, while they are captured in close proximity of time, they are not the same value and can drift by a second or so.
Changed in trove: | |
status: | Fix Committed → Confirmed |
importance: | Undecided → Critical |
Changed in trove: | |
milestone: | none → icehouse-1 |
Changed in trove: | |
milestone: | icehouse-1 → icehouse-2 |
Changed in trove: | |
status: | Fix Committed → Confirmed |
Changed in trove: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in trove: | |
milestone: | icehouse-3 → icehouse-rc1 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | icehouse-rc1 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/50192
Review: https:/