Bug #724

onedb fails when the destination sqlite file does not exist

Added by Carlos Martín almost 10 years ago. Updated almost 10 years ago.

Status:ClosedStart date:07/14/2011
Priority:NormalDue date:
Assignee:Daniel Molina% Done:

100%

Category:CLI
Target version:Release 3.0
Resolution:fixed Pull request:
Affected Versions:

Description

The command should end when the file is not found. Instead, it continues and fails to read data from the DB.

$ onedb version -v
File /var/lib/one/one.db doesn't exist.
Database schema does not look to be created by OpenNebula:
table user_pool is missing or empty.
/usr/lib/one/ruby/onedb/onedb_backend.rb:246:in `connect_db': unhandled exception

Associated revisions

Revision 3470ecf7
Added by Daniel Molina almost 10 years ago

bug #724: Improve onedb error handling

History

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

  • Category set to CLI
  • Target version set to Release 3.0

#2 Updated by Daniel Molina almost 10 years ago

  • Assignee changed from Carlos Martín to Daniel Molina
  • % Done changed from 0 to 100
  • Resolution set to fixed

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

  • Status changed from New to Closed

Also available in: Atom PDF