Bug #871

onedb reports locked table while running upgrade from 2.0 to 3.0 and fails

Added by Jan Horacek almost 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:10/05/2011
Priority:NormalDue date:
Assignee:Carlos Martín% Done:

0%

Category:Core & System
Target version:Release 3.2 - S0
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.0

Description

error message:

[oneadmin@cloudmgmt onedb]$ onedb upgrade -v -f
Version read:
2.0 : Could not read any previous db_versioning data, assuming it is an OpenNebula 2.0 or 2.2 DB.

Sqlite database backup stored in /var/lib/one/one.db.bck
Use 'onedb restore' or copy the file back to restore the DB.
> Running migrator /usr/lib/one/ruby/onedb/2.0_to_2.9.80.rb
SQLite3::SQLException: table host_shares already exists

one30-onedb-locking-error-while-db-upgrade-fix.diff Magnifier - one30-onedb-locking-error-while-db-upgrade-fix.diff (2.06 KB) Jan Horacek, 10/05/2011 05:24 PM

Associated revisions

Revision 9ed5b738
Added by Carlos Martín over 9 years ago

Bug #848: Take into account bug #871, avoid table lock

Revision a61cd0bb
Added by Carlos Martín over 9 years ago

Bug #871: Avoid locked tables in onedb upgrade. Thanks to jan horacek <>

Revision 2d820f67
Added by Carlos Martín over 9 years ago

Bug #871: Avoid locked tables in onedb upgrade. Thanks to jan horacek <>

History

#1 Updated by Jan Horacek almost 10 years ago

after fix (diff attached) it completed without error:

[oneadmin@cloudmgmt onedb]$ onedb upgrade -v -f
Version read:
2.0 : Could not read any previous db_versioning data, assuming it is an OpenNebula 2.0 or 2.2 DB.

Sqlite database backup stored in /var/lib/one/one.db.bck
Use 'onedb restore' or copy the file back to restore the DB.
> Running migrator /usr/lib/one/ruby/onedb/2.0_to_2.9.80.rb
> Done

> Running migrator /usr/lib/one/ruby/onedb/2.9.80_to_2.9.85.rb
  > Done
> Running migrator /usr/lib/one/ruby/onedb/2.9.85_to_2.9.90.rb
  > Done
> Running migrator /usr/lib/one/ruby/onedb/2.9.90_to_3.0.0.rb
  > Done

Database migrated from 2.0 to 3.0.0 (OpenNebula 3.0.0) by onedb command.

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

  • Target version set to Release 3.4

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

  • Target version changed from Release 3.4 to Release 3.2 - S0

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

  • Category set to Core & System

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

  • Status changed from New to Closed
  • Assignee set to Carlos Martín
  • Resolution set to fixed

Now in master

Also available in: Atom PDF