Rekhu Builder restarts Odoo when new Python must load

Odoo reads a module's Python only when the server starts. An upgrade brings the database up to date with the new views, fields and data, but the running server keeps the old code until it restarts. Until now, Rekhu Builder could only tell you so, and the work waited until someone with access to the hosting restarted the server.

Rekhu Builder 1.0.7 restarts the server itself.

How it works

After a change to Python, the upgrade answers that the server must restart. The builder then uses its new tool, server-restart:

• On staging and production it first tells you that the server is away for everyone for a few seconds to half a minute, and waits for your yes in the chat, as it does before an upgrade.
• It uses Odoo's own restart: the same database and the same settings, and open pages reconnect by themselves.
• It waits until the server answers again from a fresh process, and checks that the new Python is the code that runs. Only then does it go on with the tests or the next step.

On a server started with --dev=reload, Odoo restarts by itself, as before.

Through the listener

Most servers are not reachable from the internet, so the builder works through the listener, a small process next to Odoo. The listener reaches the server on its own port on the same machine or Kubernetes pod. When it runs elsewhere, such as in another Docker container, set the address once under Settings → Rekhu Builder → Advanced → Server address (for example http://odoo:8069). The call is signed with the database's own secret, like every call from Rekhu.

Also in this release

• The builder's look at the database (context) says whether the server runs older Python than its files. Through the listener this came from the listener itself, which restarts after every upgrade, so a server that still needed a restart could look up to date.

Update the module from the Rekhu for Odoo page, or pull the new version where you installed it.