Scheduling a router on a particular chassis would fail on OVSDB <= 2.8

Bug #1736941 reported by Daniel Alvarez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Invalid
Undecided
Unassigned

Bug Description

This patch [0] introduced a new dependency on the new schema defined in OVS 2.8 where we assume that 'gateway_chassis' column exists in Logical_Router_Port table in NBDB. While it doesn't crash if we're using OVS 2.7, it won't maintain the old behavior of writing the selected chassis in the external_ids column [1].

[0] https://github.com/openstack/networking-ovn/commit/d40470a51314fc0c60353c9882e0d2d44c9d2aa5
[1] https://review.openstack.org/#/c/486971/11/networking_ovn/common/ovn_client.py@712

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

The review that introduced that change, also introduced https://review.openstack.org/#/c/486971/11/networking_ovn/ovsdb/commands.py@358

Which means, that when that column doesn't exist, an exception will be captured, and the options:redirect-chassis will be inserted instead.

It's working if you try with an RDO deployment and OVS 2.7.x you may see it. Otherwise, our L3 / FIPs etc wouldn't be passing any test properly.... or we wouldn't have found the "scheduled to compute" issues that we found too when computes had not connectivity, but the router was scheduled to them.

:-)

Do I make any sense? :)

Revision history for this message
Daniel Alvarez (dalvarezs) wrote :

Sorry, closing it as invalid. It's handled in _add_gateway_chassis ovsdb/commands.py

Changed in networking-ovn:
status: New → Invalid
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.