This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 1839790 - [rfe] allow os-net-config to unconfigure previously managed interfaces that are no longer used or that are changed
Summary: [rfe] allow os-net-config to unconfigure previously managed interfaces that a...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 16.0 (Train)
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-25 14:52 UTC by David Hill
Modified: 2024-12-05 13:18 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-12-05 13:17:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-2577 0 None None None 2022-07-25 14:32:17 UTC
Red Hat Issue Tracker OSP-33139 0 None None None 2024-12-05 13:18:55 UTC
Red Hat Issue Tracker   OSPRH-12238 0 None None None 2024-12-05 13:17:16 UTC
Red Hat Knowledge Base (Solution) 5102711 0 None None None 2020-05-25 14:59:12 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.