Nightly builds version does not match openerp/release.py or the database version

[jehan]

- install debian package openerp_7.0-20130430-232443-1_all
- create a database with demo data
- watch server log

outcome: you will see periodic messages like
2013-05-01 17:30:16,751 9507 WARNING test openerp.addons.base.ir.ir_cron: Skipping database test as its base version is not 7.0.1.3.

[Guilherme Lindner (gui666)]

Exactly the same problem here, just updated today my openerp installation.

[Vo Minh Thu (thu)]

Please when reporting a bug, and stating that it is a problem, specify what you expect or at least why you think it is a bug.

OpenERP is reporting in the log that its cron process will not handle a database because that database was installed with a different version of OpenERP than the version of the cron process. This is perfectly normal behavior.

Do you mean you expect any version of OpenERP to handle any previously installed database ?

Do you mean you are surprised it tries to handle that database ?

Do you mean you are surprised it logs such event ?

[Vo Minh Thu (thu)]

One reason you might be surpised is that OpenERP "release" information has been changed recently in trunk. Its version is now 8.0 alpha. So indeed its cron process won't handle a 7.0 database.

[Vo Minh Thu (thu)]

I didn't notice it was a debian nightly build.

Probably there is a mismatch bewteen the package version, the openerp/release.py version, and the version registered in the database. Did this happen with a database installed with the aforementioned package, or with a previously installed database ?

[jehan (jens-e-hansen)]

this happens if you upgrade from debian package
openerp_7.0-20130417-232500-1_all.deb to package
openerp_7.0-20130430-232443-1_all.deb or newer.

affected are all databases installed prior to the update.

new databases installed after the update to openerp_7.0-20130430-232443-1_all.deb are not affected.

expected outcome: upgrade migrates older openerp database tables

[jehan (jens-e-hansen)]

for me a

openerp-server --update=all --database=DB_NAME

solved this issue