We just troubleshooted (and fixed) a weird issue with ipamallocation. It looked like ipallocations we're not properly removed from the ipamallocation table.

This caused port creations to fail with an error about the IP being already allocated (when there wasn't an actual port using the IP).

We found this old issue https://bugs.launchpad.net/neutron/+bug/1884532 but not a whole lot of details in there.

Has anyone seen this before?

Thanks!