Bug #2276

sqlite onedb restore fails unless db target exists

Added by Matthew Richardson almost 8 years ago. Updated almost 8 years ago.

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


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


If you call onedb restore when there is no sqlite db file already present, restore fails. However, this is a common requirement if you are rebuilding your opennebula frontend, and restoring from backup onto a clean filesystem. However, if you create an (empty) file to get round this, onedb complains that the db already exists, and you have to use 'force' to overwrite it.

Steps to reproduce (clean build, no /var/lib/one/one.db present):

$ onedb restore -s /var/lib/one/one.db /path/to/one.db.bck
[FAIL] opennebula: Restore Failed: File /var/lib/one/one.db doesn't exist

$ touch /var/lib/one/one.db
$ onedb restore -s /var/lib/one/one.db /path/to/one.db.bck
File /var/lib/one/one.db exists, use -f to overwrite.

Associated revisions

Revision 50fab833
Added by Carlos Martín almost 8 years ago

Bug #2276: onedb restore does not require the sqlite file to exist


#1 Updated by Carlos Martín almost 8 years ago

  • Category set to Core & System
  • Status changed from Pending to New
  • Assignee set to Carlos Martín
  • Target version set to Release 4.4

#2 Updated by Carlos Martín almost 8 years ago

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

Also available in: Atom PDF