Bug #3235

Delete --recreate coming from Stop state should not attempt a resume

Added by Tino Vázquez about 6 years ago. Updated over 5 years ago.

Status:ClosedStart date:10/09/2014
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:Release 4.14
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.8

Description

Now it does becuase it attends to previous history, but it should do normal boot (deploy) instead of a resume since the disks are dropped (PROLOG needs to happen again).


Related issues

Related to Bug #2488: A failed resume action will destroy and recreate the VM o... Closed 11/21/2013
Related to Feature #3654: Implement extra VM state transitions Closed 03/06/2015

Associated revisions

Revision 8dbd5380
Added by Ruben S. Montero over 5 years ago

bug #3235: Do PROLOG instead of PROLOG_RESUME after delete-recreating a VM

History

#1 Updated by Carlos Martín about 6 years ago

  • Related to Bug #2488: A failed resume action will destroy and recreate the VM on the next resume added

#2 Updated by Ruben S. Montero almost 6 years ago

  • Status changed from Pending to New
  • Target version deleted (Release 4.10)

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

  • Related to Feature #3654: Implement extra VM state transitions added

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

  • Status changed from New to Closed
  • Target version set to Release 4.14
  • Resolution set to fixed

Also available in: Atom PDF