Skip to main content

Updating Antelao

Checking​

Local only
# odoocli server update

server update is read-only. It reports newer container images and newer apt packages and changes nothing. The console shows the same on its Updates page.

Applying​

Local only
# odoocli server upgrade

Both commands must run on the host, not inside a container: applying an upgrade recreates the API's own container, and a process cannot reliably replace the container it is running in.

Order of operations​

  1. Take a backup of the master database. This is the step people skip, and the one that makes rollback possible.
  2. odoocli server update to see what would change.
  3. odoocli server upgrade.
  4. Re-run odoocli server install if you also want the console's self-signed certificate reissued, since that only happens at install time.

Rollback is not just the old package​

The master database schema upgrade is forward-only

A newer release may upgrade the master database schema on first start. An older binary then refuses to start against it.

Rolling back therefore means restoring the master database from before the upgrade, as well as reinstalling the previous version. Without that backup there is no rollback.

Release notes​

Local only
# odoocli release-notes

The same notes are on the console's Release notes page. They are built into the product itself rather than fetched, so they always describe the version you are actually running.

Instances are not upgraded by this​

server update and server upgrade cover Antelao. Upgrading an Odoo instance to a newer Odoo major version is a separate exercise involving Odoo's own migration path, and is not something this product performs for you.

What it does give you is the safe way to attempt one: clone the database, point a new instance at the clone, and try the migration there.

Last updated on