v50 upgrade: run database migrations

[inghamn]

I'm working on upgrading our installation. We've been on v47 for a while now.

So far, it seems like I very much need to upgrade one release version at a time, in order to run the database migrations. I've been able to upgrade 47->48->49 with not much trouble. However 49->50 does not seem to run any database migrations. When I start up v50, we get database errors from missing tables:

psycopg2.errors.UndefinedTable: relation "product" does not exist

Is there a way to run the database migrations manually? Or some other process that should be done for a v49->v50 upgrade?

[bobintetley]

Every release has all of the database updates for every previous release, so you're fine to go straight from 47 to 50.

What we stopped doing in 50 is checking for and running database updates automatically through the UI since it was a bit of a waste and could lead to race conditions.

You should be able to run the cron.py script from the install directory and tell it to run all updates:

python3 cron.py maint_db_update

[inghamn]

Thank you so much, that makes perfect sense. Running maint_db_update manually seems to have worked and asm starts up cleanly now.

[traviswparker]

This needs to be clearly stated at the top of the release notes because I thought i was going to have to revert to 49 and hope that brought the rescue I do IT for back up... I think there is a way to make dpkg run a shell command on package upgrade, maybe do that?

[bobintetley]

Thanks, this is a good suggestion. I've added this for the next release. I'll update the release notes.