Bug 1311983 - VM uptime is wrong on BR44 report
VM uptime is wrong on BR44 report
Product: ovirt-engine-reports
Classification: oVirt
Component: Reports (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: ovirt-3.6.5
: ---
Assigned To: Shirly Radco
Pavel Stehlik
: ZStream
Depends On: 1304656
  Show dependency treegraph
Reported: 2016-02-25 07:44 EST by Shirly Radco
Modified: 2016-02-25 08:12 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1304656
Last Closed: 2016-02-25 08:12:38 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Reports
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
sradco: ovirt‑3.6.z?
ylavi: planning_ack+
sradco: devel_ack?
sradco: testing_ack?

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 53839 None None None 2016-02-25 07:44 EST

  None (edit)
Description Shirly Radco 2016-02-25 07:44:03 EST
+++ This bug was initially created as a clone of Bug #1304656 +++

Description of problem:
Open BR44 report and notice the difference between Existence time and VM uptime, which is higher for some cases.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. have some VM's up and running for some time
2. open BR44 report
3. notice difference between VMs uptime and existence time

Actual results:
some VM's have higher uptime than existence time

Expected results:
VMs uptime to be reported correctly

Additional info:

--- Additional comment from Shirly Radco on 2016-02-08 04:33:02 EST ---

Can you attach screenshut, History db dump and and expected values in report?

--- Additional comment from Petr Matyáš on 2016-02-08 08:08 EST ---

--- Additional comment from Petr Matyáš on 2016-02-08 08:17 EST ---

And for the expected values it's obvious, not higher Uptime of VM than VM's Existing time.

Note You need to log in before you can comment on or make changes to this bug.