queue_job_lock table not created on install — causes psycopg2.errors.UndefinedTable in jobrunner requeue

[django-frog]

Summary

After installing the latest version of queue_job (post-September 2025 batch), the jobrunner fails with a psycopg2.errors.UndefinedTable error because the table queue_job_lock is never created — even on a fresh database installation.

The model queue.job.lock is correctly defined and imported, but the corresponding SQL table does not exist in PostgreSQL.

Traceback

Traceback (most recent call last):

  File "/mnt/extra-addons/queue_job/jobrunner/runner.py", line 601, in run

    self.requeue_dead_jobs()

  File "/mnt/extra-addons/queue_job/jobrunner/runner.py", line 507, in requeue_dead_jobs

    db.requeue_dead_jobs()

  File "/mnt/extra-addons/queue_job/jobrunner/runner.py", line 404, in requeue_dead_jobs

    cr.execute(query)

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

LINE 45:                         queue_job_lock

Environment

• Odoo version: 18.0 (Enterprise)
• queue_job version: main branch, latest (October 2025)
• Python: 3.12
• PostgreSQL: 12
• Deployment: Dockerized Odoo environment

[amh-mw]

@django-frog A fresh odoo --init=queue_job creates the queue_job_lock table. Perhaps odoo --update=queue_job (or similar in user interface Apps menu)?

[django-frog]

@amh-mw , Thank you so much

But I don't know if we can do this on Odoo.sh, how can we initialize this table in Odoo.sh ?

[simahawk]

you can run that in the shell on odoo sh. Just get to the shell and use odoo-bin https://www.odoo.com/documentation/19.0/administration/odoo_sh/advanced/containers.html#run-an-odoo-server
However. that table comes from a normal model: an upgrade should do the trick. Either from the UI or from the shell.