Uptime/VCPU hours of stopped Instances Keep on increasing even if instance satus is in shutdown mode

Bug #1156563 reported by krypto
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Matthias Runge

Bug Description

I am using Folsom on Ubunru 12.04 with Horizon.

Created 5 instances on KVM on 12.04 (running nova-compute only )and with out stopping VM, restarted Host machine.
Under Instance Tab status of all instance is Shutdown but under "Overview" Uptime of VM keeps on increasing.
Same in case of VCPU hours.

Tags: ux
Revision history for this message
Gabriel Hurley (gabriel-hurley) wrote :

They are currently based on the created_at time, which is definitely not ideal. We should revisit this in H.

Changed in horizon:
importance: Undecided → Medium
milestone: none → havana-1
status: New → Confirmed
Revision history for this message
Tihomir Trifonov (ttrifonov) wrote :

The uptime is calculated in nova... so not much to do in Horizon... In fact the 'uptime' might need to be defined what means for OpenStack - is it the total time the instance is being alive in the virt manager(either running or shut off) - which is the current definition, or the total time the instance is being active(power state == RUNNING)...

Changed in horizon:
milestone: havana-1 → havana-2
Changed in horizon:
milestone: havana-2 → havana-3
Lawrance (jing)
Changed in horizon:
assignee: nobody → Lawrance (jing)
Changed in horizon:
milestone: havana-3 → none
Lawrance (jing)
Changed in horizon:
assignee: Lawrance (jing) → nobody
Changed in horizon:
assignee: nobody → Santiago Baldassin (santiago-b-baldassin)
Revision history for this message
Santiago Baldassin (santiago-b-baldassin) wrote :

This is not a valid bug. Uptime actually reflects the time since the instance was created, maybe the title is misleading but the value is correct. Vcpu hours are returned by nova, horizon just displays what nova returns

Changed in horizon:
status: Confirmed → Invalid
Revision history for this message
Julie Pichon (jpichon) wrote :

Since it causes enough confusion that people open bug reports, we should rename the column. Any suggestion on what would be appropriate? "Time since creation" sounds like it should be good enough.

Changed in horizon:
assignee: Santiago Baldassin (santiago-b-baldassin) → nobody
status: Invalid → Confirmed
tags: added: ux
removed: horizon uptime
Revision history for this message
Ashish Chandra (ashish-chandra) wrote :

I second Julie, Renaming the column would be better option.

Changed in horizon:
assignee: nobody → Ashish Chandra (ashish-chandra)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/125332

Changed in horizon:
assignee: Ashish Chandra (ashish-chandra) → Matthias Runge (mrunge)
status: Confirmed → In Progress
Revision history for this message
Matthias Runge (mrunge) wrote :

This is a prominent issue, confusing users.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/125332
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=b5b09140b1906d6fc401493908003f6312d720a9
Submitter: Jenkins
Branch: master

commit b5b09140b1906d6fc401493908003f6312d720a9
Author: Matthias Runge <email address hidden>
Date: Wed Oct 1 14:00:31 2014 +0200

    Change column uptime

    Renamed misleading column uptime

    Change-Id: Id72c10a7166943fcfef68c338a1412897ad9cc4b
    Closes-Bug: #1156563

Changed in horizon:
status: In Progress → Fix Committed
Akihiro Motoki (amotoki)
Changed in horizon:
milestone: none → juno-rc1
Thierry Carrez (ttx)
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: juno-rc1 → 2014.2
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.