Bug 1839790

Summary:	[rfe] allow os-net-config to unconfigure previously managed interfaces that are no longer used or that are changed
Product:	Red Hat OpenStack	Reporter:	David Hill <dhill>
Component:	os-net-config	Assignee:	OSP Team <rhos-maint>
Status:	NEW ---	QA Contact:	Nobody <nobody>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16.0 (Train)	CC:	bfournie, cgussobo, hbrock, jkreger, jslagle, mburns
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	x86_64
OS:	Linux
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 David Hill 2020-05-25 14:52:26 UTC

Description of problem:
[rfe] allow os-net-config to unconfigure previously managed interfaces that are no longer used or that are changed.   In the current use case, customer managed to have bond0 and bond1 in br-ex and it created a network loop.   The proper way of applying those changes would've been to remove the current configuration and then apply the new one in order to avoid potential network loops. 

Another solution would've been to execute many deployemnt/manual steps to transition to the new configuration in order to avoid that possibility.    




Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Manage to get 2 interfaces in the same bridge that shouldn't be.
2.
3.

Actual results:
Network loop / network outage

Expected results:
Failsafe against that

Additional info: