Comment 3 for bug 2000378

OK, I see the problem now: the OVN LSP leftover is "76ff3324-7326-412d-bdc9-df5db5adcf84". When a new LSP is created in the same network and with the same IP addresses, it is assigned as "virtual" to the leftover.

In this case I'll state that the ML2/OVN code is not expecting this kind of leftovers. This is something wrong in the system that should be solved outside this code. The maintenance task is not fixing this issue neither. I would suggest to anyone taking this bug to consider removing those OVN DB items that have Neutron information but are no longer referred in the Neutron DB; this LSP is a good example.

For now the only solution that I can offer is what you already did: to manually clean the OVN DB, after the simulated failure.