Removing nova-compute with ovn-chassis related doesn't cleanup neutron agents
Bug #1933486 reported by
Diko Parvanov
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-ovn-chassis |
New
|
Undecided
|
Unassigned |
Bug Description
Cleanly removing nova-compute unit with juju remove-unit with related ovn-chassis charm leaves openstack network agents ovn-controller and networking-
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-
ovn-common 20.03.2-
tags: | added: scaleback |
To post a comment you must log in.
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.