Bug #350

Core method saveas should check VM consistency

Added by Javi Fontan almost 11 years ago. Updated almost 10 years ago.

Status:ClosedStart date:09/15/2010
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:


Category:Core & System
Target version:Release 3.0
Resolution:fixed Pull request:
Affected Versions:


onevm saveas deals with this problem but the core should also do it.

From Bug #347:

There is some room for improvement in save as:

1.- Roll back: If for any reason the saveas method fails in the core the image has to be deleted

2.- Persistent images already uses saveas. CLI should not allow to saveas a persistent image as it is going to be saveas already

3.- If a VM has been marked as to be savedas subsequent calls to saveas should fail at the API level.

Related issues

Related to Bug #347: onevm saveas should check VM consistency Closed 09/12/2010
Related to Feature #489: Customize "saveas" image saving command to cater for spec... Closed 02/21/2011


#1 Updated by Carsten Friedrich over 10 years ago

regarding (1), I don't think the image should be deleted; it may contain work which has not been saved otherwise. Maybe it should instead be moved to s special area where it can be recovered from manually, but removed from the repository.

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

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

This issues have been addressed in the new image repository for OpenNebula 3.0

Also available in: Atom PDF