Comment 5 for bug 1859887

I can't find a particular commit, it just seemed like a race condition in the agent that we fixed.

Just so it's clear, in order to reproduce this do you have to:

1) associate a floating IP
2) dis-associate that floating IP

In other words, the rule was created in 1) but not cleaned-up in 2)

If this is the case, can you attach relevant parts of the l3-agent.log for both operations for a new port? Especially look for any tracebacks. This would need to be done with debug enabled so all the messages are printed.

Thanks