uptime calculation in simple_usage is incorrect

Bug #921807 reported by Anthony Young
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Low
Anthony Young

Bug Description

The uptime of a server is reported as:

info['uptime'] = delta.days * 24 * 60 + delta.seconds

The correct calculation is:

info['uptime'] = delta.days * 24 * 60 * 60 + delta.seconds

Changed in nova:
assignee: nobody → Anthony Young (sleepsonthefloor)
status: New → In Progress
Changed in nova:
importance: Undecided → Low
milestone: none → essex-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/3428
Committed: http://github.com/openstack/nova/commit/093c147a14059c60e6b787589398ee7d8f9792d9
Submitter: Jenkins
Branch: master

commit 093c147a14059c60e6b787589398ee7d8f9792d9
Author: Anthony Young <email address hidden>
Date: Wed Jan 25 12:30:09 2012 -0800

    Fix uptime calculation in simple_usage

     * Fixes bug 921807

    Change-Id: Ie6460adb95ef3b9cb0473023816c255aac707e99

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (milestone-proposed)

Fix proposed to branch: milestone-proposed
Review: https://review.openstack.org/3449

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (milestone-proposed)

Reviewed: https://review.openstack.org/3449
Committed: http://github.com/openstack/nova/commit/2b06655d3946e0594dd0bd23b637930cfcfc8568
Submitter: Jenkins
Branch: milestone-proposed

commit 2b06655d3946e0594dd0bd23b637930cfcfc8568
Author: Anthony Young <email address hidden>
Date: Wed Jan 25 12:30:09 2012 -0800

    Fix uptime calculation in simple_usage

     * Fixes bug 921807

    Change-Id: Ie6460adb95ef3b9cb0473023816c255aac707e99

Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: essex-3 → 2012.1
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.