[OSA][Bobcat] Masakari DB Sync Error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Committed
|
High
|
Unassigned |
Bug Description
Masakari deployment fails on a fresh install on Debian 12 with the following:
fatal: [host01_
04:42.245634", "msg": "non-zero return code", "rc": 1, "start": "2024-02-04 11:04:41.942779", "stderr": "Traceback (most recent call last):\n File \"/openstack/
ine 5, in <module>\n from masakari.cmd.manage import main\n File \"/openstack/
y import migration\n File \"/openstack/
\nModuleNotFoun
akari.cmd.manage import main", " File \"/openstack/
\"/openstack/
No module named 'migrate'"], "stdout": "", "stdout_lines": []}
This is because sqlalchemy-migrate isn't installed to the venv.
Adding sqlalchemy-migrate to pip packages fixes the issue:
/etc/ansible/
masakari_
- .....
- sqlalchemy-migrate
Haven't submitted a fix as not sure if this affects other os's etc...
Apologies if this isn't set out right, my first bug report :)
Changed in openstack-ansible: | |
status: | New → Triaged |
Changed in openstack-ansible: | |
status: | Triaged → In Progress |
importance: | Undecided → High |
Changed in openstack-ansible: | |
status: | In Progress → Fix Committed |
Hey,
From what I can recall there's a bug in masakari related to incompatibility with sqlalchemy version, which also was hitting masakari ci, and fixes of that were merged only for master.
We will triage this bug report accordingly during the week, but highly likely that the best way would be just to using "master" (future 2024.1) version of masakari.
For that you can define a variable under user_variables.yml:
masakari_ git_install_ branch: 6b38affa154f82f 885190a70770581 aadf6d7dd4
PS: oh, ok, indeed adding sqlalchemy-migrate would be more trivial fix, I will verify it works and propose patch shortly