diff options
| author | Michael Kerrin <michael.kerrin@hp.com> | 2013-06-06 08:52:52 +0000 |
|---|---|---|
| committer | Michael Kerrin <michael.kerrin@hp.com> | 2013-06-07 16:03:09 +0000 |
| commit | 4aee80dd31131675ae0ab9f927b2d4aed0b8426a (patch) | |
| tree | 4baaf55a8b2ef11a24e884018f644d689c06fd8c /nova/utils.py | |
| parent | 7a475d3cd606e68090075c1a8944e3aeb7898b87 (diff) | |
| download | nova-4aee80dd31131675ae0ab9f927b2d4aed0b8426a.tar.gz nova-4aee80dd31131675ae0ab9f927b2d4aed0b8426a.tar.xz nova-4aee80dd31131675ae0ab9f927b2d4aed0b8426a.zip | |
Sending volume IO usage broken
This is my fault, I didn't test the sending of notifications
enough when fixing bug 1182102, when the volume IO usage notifications
were been sent too often. This was merged as part of
https://review.openstack.org/#/c/29915
The issue was that the code worked for the first IO usage event (the
one I looked at). Then when constructing the event payload for the second
and following IO usage events the code path ended up comparing a datetime
object from the db with a cached string representation of the last_refreshed
date that was passed into the conductor via the RPC.
Since last_refreshed argument to vol_usage_update in the db layer is
not needed and is causing these issues. I have removed last_refreshed
argument from the db layer and deprecated it from the conduction API.
Change-Id: I2030eb7912c56134ea688a6e8bbfcdeddca28307
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions