novaclient record request time even when timing is set to False

Bug #1433490 reported by ZhiQiang Fan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-novaclient
New
Undecided
Unassigned

Bug Description

The expected behavior is when timing is True, then we record each request's time, then we should call reset_timings() to clear memory

However, the v1_1.client record each request's time no matter what timing is set, then after long running time in service like ceilometer-agent-compute, the memory keeps increasing

We'd better not record request's time when timing is set to False

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.