Bug 1777896

Summary: [RFE] Force subport deletion
Product: Red Hat OpenStack Reporter: Luis Tomas Bolivar <ltomasbo>
Component: openstack-neutronAssignee: OSP Team <rhos-maint>
Status: NEW --- QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16.0 (Train)CC: amoralej, chrisw, scohen, skaplons
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luis Tomas Bolivar 2019-11-28 15:57:11 UTC 
From the OpenShift on OpenStack with Kuryr use case point of view, it would be great to be able to force the deletion of a subport associated to a trunk. All the OpenShift pods are connected to the Neutron networks through subports, which are attached to the trunk whose parent port is used for the VM where the pod is running. Thus creating and removing subports is a really common action.

There is information about the subports in the trunk, however, there is no information on the subports about the trunk they belong too. This means Kuryr needs to:
1) retrieve information from neutron about the current trunks and their attached subports. And then filter the one where the port is attached to
2) detach it from the trunk,
3) and finally remove it.

It will be great to allow the deletion of subports attached to trunks without having to detach them from their trunk first, perhaps with extra flag: --detach or --force.