Removing nova-compute with ovn-chassis related doesn't cleanup neutron agents

[Diko Parvanov]

Cleanly removing nova-compute unit with juju remove-unit with related ovn-chassis charm leaves openstack network agents ovn-controller and networking-ovn-metadata-agent with XXX / UP and those can't be deleted with openstack network agent delete

Not found is ovn-sbctl show list, so can't be deleted manually either

Remove hook should clean those remaining entries up.

ovn-chassis revision 14
ovn-central revision 7

bionic/ussuri
ovn-central 20.03.2-0ubuntu0.20.04.1~cloud0
ovn-common 20.03.2-0ubuntu0.20.04.1~cloud0

[Drew Freiberger (afreiberger)]

Workaround is to recycle neutron-server.service on neutron-api servers.

The issue seems to be that neutron doesn't sync with OVN properly after the service is started. Any removals of chassis in OVN DB doesn't get reflected in neutron until the next sync cycle which defaults to the start of the neutron-server process.

I think a solution will have to be created to have ovn-central's relation to neutron-api affect a service recycle after the chassis is removed from the OVN SouthboundDB.

[Paul Goins (vultaire)]

I've hit this issue as well.

[Peter Matulis (petermatulis)]

My understanding is that this is due to an upstream Neutron bug and that it has been fixed in newer releases. Apologies for not having references for this.

[Felipe Reyes (freyes)]

As workaround it's possbible to remove a chassis from the southbound database with the following command:

sudo ovn-sbctl chassis-del <CHASSIS_NAME>