Trunk Deletion is failing with error that it is currently in use.

Solution Verified - Updated -


  • The trunk cannot be deleted as it’s parent port is still bound to a deleted host thus further also not allowing network to be deleted as there trunks are build on those networks.
(oscar23) [id921356@el6266  ~]$ o network trunk delete b3b155d6-678c-4aba-81f5-ed4d0af27e2fFailed to delete trunk with name or ID 'b3b155d6-678c-4aba-81f5-ed4d0af27e2f': Trunk b3b155d6-678c-4aba-81f5-ed4d0af27e2f is currently in use.
> Neutron server returns request_ids: ['req-aceb5362-1ade-4b94-b099-ab6fc851cd60']
> 1 of 1 trunks failed to delete.
  • VM deletion failes and gives folliwng error if the parent port of trunk is associated with the VM itself during it’s creation.
> 2020-03-04 09:52:46.257 1 WARNING [req-0dd45fe4-861c-46d3-a5ec-7db36352da58 02c6d1bc10fe4ffaa289c786cd09b146 695c417810ac460480055b074bc41817 - default default] [instance: 2f9e3740-b425-4f00-a949-e1aacf2239c4] Failed to delete port 991e4e50-481a-4ca6-9ea6-69f848c4ca9f for instance.: Conflict: Port 991e4e50-481a-4ca6-9ea6-69f848c4ca9f is currently a parent port for trunk 5800ee0f-b558-46cb-bb0b-92799dbe02cf


RedHat OpenStack Platform 13 (RHOSP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content