Agent API gets broken if OVN DB is upgraded to the one introducing chassis_private

Bug #1901527 reported by Jakub Libosvar
6
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: ovn
tags: added: ovn
Changed in neutron:
assignee: nobody → Jakub Libosvar (libosvar)
Changed in neutron:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Bence Romsics (bence-romsics) wrote :

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...

Revision history for this message
Jakub Libosvar (libosvar) wrote :

Yes, chassis_private improves scalability big time. The schema is defined in OVN Db processes, the problem is only when those processes are restarted on new schema while neutron-server keeps running. Restarting neutron-server fixes the problem.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to neutron (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/760962

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Related fix proposed to branch: master
Review: https://review.opendev.org/760963

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.opendev.org/760967

Changed in neutron:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Jakub Libosvar (<email address hidden>) on branch: master
Review: https://review.opendev.org/760963

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Jakub Libosvar (<email address hidden>) on branch: master
Review: https://review.opendev.org/760962

Revision history for this message
Lucas Alvares Gomes (lucasagomes) wrote :
Revision history for this message
Jakub Libosvar (libosvar) wrote :

Yes, I think it's https://review.opendev.org/c/openstack/neutron/+/760967 but you're right, it's fixed now. Thanks for pointing it out!

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 18.0.0.0rc1

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.