[nova][neutron][ptg] Summary: Leaking resources when ports are deleted out-of-band
balazs.gibizer at ericsson.com
Fri May 3 21:35:23 UTC 2019
On Fri, May 3, 2019 at 3:20 PM, Eric Fried <openstack at fried.cc> wrote:
> Summary: When a port is deleted out of band (while still attached to
> instance), any associated QoS bandwidth resources are orphaned in
> - Neutron to block deleting a port whose "owner" field is set.
> - If you really want to do this, null the "owner" field first.
> - Nova still needs a way to delete the port during destroy. To be
> discussed. Possibilities:
> - Nova can null the "owner" field first.
> - The operation can be permitted with a certain policy role, which
> Nova would have to be granted.
> - Other?
1) Nova will log an ERROR when the leak happens. (Nova knows the
port_id and the RP UUID but doesn't know the size of the allocation to
remove it). This logging can be added today.
2) Matt had a point after the session that if Neutron enforces that
only unbound port can be deleted then not only Nova needs to be changed
to unbound a port before delete it, but possibly other Neutron
More information about the openstack-discuss