RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):
vdsm-4.9.6-38.0.el6_3

How reproducible:
100%

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
  
Actual results:
The logged lastCheck value is a timestamp.

Expected results:
The logged lastCheck value is a delta value (the same reported and displayed by vdsClient -s 0 getVdsStats).

commit a3279c486ca289adbcaacb80ceaca735d7a9c60d
Author: Federico Simoncelli <fsimonce>
Date:   Thu Sep 13 09:10:35 2012 -0400

    stats: move the lastCheck computation to getRepoStats
    
http://gerrit.ovirt.org/#/c/7993/

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.

http://rhn.redhat.com/errata/RHSA-2012-1508.html