Bug #1210

Failure to resume dooms the checkpoints

Added by Tino Vázquez about 9 years ago. Updated over 8 years ago.

Status:ClosedStart date:04/09/2012
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:-
Target version:Release 3.8
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.4

Description

From Sándor Guba

--
My problem is that if VM reach Fail state you can't do anything but to resubmit. I restarted my whole cloud and on node where the NFS mount failed, every suspended VM that I resumed and scheduled to that node failed. After that I fixed mount but couldn't find the way to resume the vms. Resubmit delete all the checkpoints wich I wanted to save. Any suggestion how to evade the image delete to start the vm?
--

A possible solution would be to make that the STOP state should not be abandoned upon failure

Associated revisions

Revision fda16abb
Added by Carlos Martín over 8 years ago

Bug #1210: Add new VM LCM state in core, BOOT_SUSPENDED. A failed boot returns the VM to SUSPENDED

Revision 6669d31f
Added by Carlos Martín over 8 years ago

Bug #1210: Add BOOT_SUSPENDED state to OCA (both Ruby & Java)

Revision 9640ed1d
Added by Carlos Martín over 8 years ago

Bug #1210: Add BOOT_SUSPENDED state to oZones and Sunstone

Revision 2f5f5813
Added by Carlos Martín over 8 years ago

Bug #1210: Add BOOT_SUSPENDED state to xsd and dot documentation files

Revision 04a4fe96
Added by Carlos Martín over 8 years ago

Bug #1210: Add new VM LCM state in core, BOOT_STOPPED. A failed boot returns the VM to EPILOG_STOP -> STOPPED

Revision ae8a1875
Added by Carlos Martín over 8 years ago

Bug #1210: Add BOOT_STOPPED state to OCA (both Ruby & Java), Sunstone and oZones

Revision c0587036
Added by Carlos Martín over 8 years ago

Bug #1210: Add BOOT_STOPPED state to xsd and dot documentation files

Revision 22e605c7
Added by Carlos Martín over 8 years ago

Bug #1210: Fix bug in 04a4fe9, a failed PROLOG_RESUME must have STOP_RESUME history reason, otherwise the transition STOPPED->PENDING->PROLOG_RESUME will end in PENDING->PROLOG

Revision 41d78ded
Added by Carlos Martín over 8 years ago

Bug #1210: On prolog failure, add the transition PROLOG_RESUME -> STOPPED

History

#1 Updated by Ruben S. Montero about 9 years ago

  • Target version set to Release 3.6

#2 Updated by Ruben S. Montero about 9 years ago

  • Assignee set to Ruben S. Montero

#3 Updated by Ruben S. Montero almost 9 years ago

  • Status changed from New to Assigned
  • Assignee changed from Ruben S. Montero to Carlos Martín

#4 Updated by Ruben S. Montero almost 9 years ago

  • Assignee changed from Carlos Martín to Javi Fontan

#5 Updated by Javi Fontan almost 9 years ago

  • Target version changed from Release 3.6 to Release 3.8

#6 Updated by Javi Fontan over 8 years ago

  • Assignee changed from Javi Fontan to Ruben S. Montero

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

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

Also available in: Atom PDF