Bug #2278

VM used CPU and memory not updated after stop

Added by Javi Fontan over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:08/24/2013
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 4.4
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.2

Description

VM used CPU and memory for a stopped VM are still the last monitored values. Should be 0.

Associated revisions

Revision 3ece9dac
Added by Carlos Martín over 5 years ago

Bug #2278: Reset cpu and memory monitorization to 0 when the VM exits the running state

Revision eb946b47
Added by Ruben S. Montero over 5 years ago

Bug #2278: Removed unneeded comment

Revision 8099694f
Added by Carlos Martín over 5 years ago

Bug #2278: Reset cpu and memory monitorization to 0 when the VM exits the running state

(cherry picked from commit 3ece9dacdf1f412cb0412d56c5367adc3894088d)

Revision 04c5f008
Added by Ruben S. Montero over 5 years ago

Bug #2278: Removed unneeded comment

(cherry picked from commit eb946b47509d672dac69bef87d2bdbeafa90dba8)

History

#1 Updated by Javi Fontan over 5 years ago

  • Status changed from Pending to New
  • Target version set to Release 4.4

#2 Updated by Carlos Martín over 5 years ago

  • Assignee set to Carlos Martín

#3 Updated by Ruben S. Montero over 5 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF