-
Epic
-
Resolution: Done
-
Undefined
-
rhos-16.2.z
-
[rfe] allow os-net-config to unconfigure previously managed interfaces that are no longer used or that are changed
-
False
-
False
-
Not Set
-
Done
-
Not Set
-
rhos-connectivity-nfv
-
Not Set
-
Undefined
-
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:
- is depended on by
-
RHOSSTRAT-660 os-net-config should resolve conflicts between ifcfg and NM connections
-
- Closed
-
- external trackers