Comment 1 for bug 1898994

As a consequence of the above problem when the server later deleted neutron fails to unbind the port so the port remains in use.

The only visible problem in the neutron log during the delete:

Oct 08 08:27:40 aio neutron-server[843]: DEBUG neutron_lib.callbacks.manager [req-61512f24-826a-424a-a866-74915d1c9d9b req-3fb1ce31-2470-4e51-b283-4928a2a87b9c service neutron] Callback neutron.services.qos.qos_plugin.QoSPlugin._check_port_for_placement_allocation_change--9223372036854757806 raised Resource provider 1110cf59-cabf-526c-bacc-08baabbac692 for cf5809b6-1dbe-43d5-8270-b734255a946e does not exist {{(pid=2968) _notify_loop /opt/stack/neutron-lib/neutron_lib/callbacks/manager.py:210}}