Agent API gets broken if OVN DB is upgraded to the one introducing chassis_private
Bug #1901527 reported by
Jakub Libosvar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Jakub Libosvar |
Bug Description
Neutron determines which table to use for agent healthchecks at the initialization phase. With OVN databases that don't implement chassis_private table a chassis table is used, which has scaling impacts.
However, if OVN DB is upgraded while Neutron is running, the healthchecks will be still performed on chassis table while OVN already uses chassis_private. This leads to reporting dead agents by the API.
We should detect OVN was upgraded and start using chassis_private table since.
tags: | added: ovn |
Changed in neutron: | |
assignee: | nobody → Jakub Libosvar (libosvar) |
Changed in neutron: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
Is the use of chassis_private always better than using the chassis table? If it is then alternatively we could just upgrade this schema on the next neutron start unconditionally. That may be simpler than detecting the upgrade and all schemas would be uniform after. Just floating the idea...