Red Hat Bugzilla – Bug 868721
Improve logging for the lastCheck value returned by getVdsStats
Last modified: 2012-12-04 14:13:19 EST
Description of problem:
At the moment when getVdsStats is received by VDSM the logged information (regarding storage domains) are the ones generated by repoStats. In particular one of the reported values, lastCheck, is logged as a timestamp instead of the actual value reported to the engine (delta seconds since last stats collection).
To improve debugging (the lastCheck is tested by the engine and countermeasures are taken if it grows over a certain limit) VDSM should log the actual value reported to the engine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. vdsClient -s 0 getVdsStats
2. check that what is logged is repoStats and lastCheck is a timestamp instead of a delta time
The logged lastCheck value is a timestamp.
The logged lastCheck value is a delta value (the same reported and displayed by vdsClient -s 0 getVdsStats).
Author: Federico Simoncelli <firstname.lastname@example.org>
Date: Thu Sep 13 09:10:35 2012 -0400
stats: move the lastCheck computation to getRepoStats
si24. fixed. repostats shows the lastcheck. value is same as in getVdsStats.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.