Bug #1280

Cache-DB inconsistency in LifeCycleManager::clean_up_vm

Added by Carlos Martín over 8 years ago. Updated over 8 years ago.

Status:ClosedStart date:05/17/2012
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.6
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.4

Description

This happens after a 'onevm delete' operation over a VM in 'failed' state.

In LifeCycleManager::clean_up_vm the history record is modified:

    vm->set_etime(the_time);
    vm->set_vm_info();
    vm->set_reason(History::USER);

This changes in the cached object must be written to the DB using

vmpool->update_history(vm);

But this is omitted in case VirtualMachine::FAILURE.

Associated revisions

Revision 7d8b9ea2
Added by Carlos Martín over 8 years ago

Bug #1280: Add update_history call to the FAILURE state

Revision 6500b92b
Added by Carlos Martín almost 8 years ago

Bug #1280: Add update_history call to the FAILURE state
(cherry picked from commit 7d8b9ea22b63f6d3bc3e81ad36f5b565439bc342)

History

#1 Updated by Ruben S. Montero over 8 years ago

  • Status changed from New to Assigned

#2 Updated by Ruben S. Montero over 8 years ago

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

Also available in: Atom PDF