Database version mismatch upgrading ONE from 4.14 beta1 to beta2

Community Support
1

Hi all

We found a database issue upgrading the current ONE 4.14 beta1 version to 4.14 beta 2, if we execute onedb upgrade we get this message:

$ onedb upgrade -v -S localhost -u oneadmin -p xxxxxxxxxxx -d opennebula
Version read:
Shared tables 4.11.80 : Database migrated from 4.6.0 to 4.11.80 (OpenNebula 4.11.80) by onedb command.
Local tables 4.13.80 : Database migrated from 4.11.80 to 4.13.80 (OpenNebula 4.13.80) by onedb command.

MySQL dump stored in /var/lib/one/mysql_localhost_opennebula_2015-9-22_10:29:0.sql
Use ‘onedb restore’ or restore the DB using the mysql command:
mysql -u user -h server -P port db_name < backup_file

Running migrators for shared tables
Database already uses version 4.11.80

Running migrators for local tables
Running migrator /usr/lib/one/ruby/onedb/local/4.13.80_to_4.13.85.rb
Done in 0.21s

But if we try to run oned service the db version is not changed and the service is not started correctly:

$ oned start
$ Database version mismatch. Check oned.log.

And from our logs:

Tue Sep 22 10:47:11 2015 [Z0][ONE][I]: Checking database version.
Tue Sep 22 10:47:11 2015 [Z0][ONE][E]: Database version mismatch ( local_db_versioning). Installed OpenNebula 4.13.85 needs DB version ‘4.13.85’, and existing DB version is ‘4.13.80’.
Tue Sep 22 10:47:11 2015 [Z0][ONE][E]: Use onedb to upgrade DB.

and the onedb fsck output seems to be ok:

$ onedb fsck -S localhost -u oneadmin -p xxxxxxxxxxxxx -d opennebula
MySQL dump stored in /var/lib/one/mysql_localhost_opennebula_2015-9-22_10:55:12.sql
Use ‘onedb restore’ or restore the DB using the mysql command:
mysql -u user -h server -P port db_name < backup_file

Total errors found: 0
Total errors repaired: 0
Total errors unrepaired: 0
A copy of this output was stored in /var/log/one/onedb-fsck.log

Is this a known issue? or something is missing in the documentation?

We have installed opennebula-server-4.13.85-2.x86_64 from opennebula repo.

Thanks in advance
Alvaro

2

Hi @alvaro_simongarcia

We are also performing the upgrade to beta2 but from ONE 4.12.

I will confirm you in the afternoon if we also get the same issue.

Thanks,
Esteban

3

Hi,

To be sure, you can also ask onedb to show the current DB version with the ‘onedb version -v’ command

Can you please double check that oned.conf is pointing to the same database? The configuration should be also at the top of oned.log.

4

Hi @cmartin @esfreire

Sorry for the noise, as @cmartin said the oned.conf was replaced by the rpm, and the log message was a bit confusing. After the oned.conf update everything went fine again :smile:

Sorry again for the noise, now we are testing the new beta

Cheers and thanks!
Alvaro

5

Hi all,

Just to confirm that we have performed the upgrade from ONE 4.12. to 4.14 beta2 and everything was smooth during the upgrade. Also, we did not find any issue during DB upgrade.

Now, as @alvaro_simongarcia, it is also time for testing :smile:

Regards,
Esteban