[RFE] IP, MTU, and route changes should not restart interfaces
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | os-net-config |
Undecided
|
Dan Sneddon | ||
Bug Description
os-net-config restarts an interface when any aspect of the configuration changes. Some changes, like IP changes, route changes, MTU, and boot settings can be set on the fly with 'ip' or 'ip route' commands. If those are the only changes, os-net-config should just make the changes to the config and run the necessary commands instead of restarting the interface.
This behavior is necessary in environments where routes may be updated during scaling operations, such as routed spine/leaf environments when adding new leaf networks.
| Changed in os-net-config: | |
| status: | New → Triaged |
| assignee: | nobody → Dan Sneddon (dsneddon) |
| Changed in os-net-config: | |
| status: | Triaged → In Progress |
| Changed in os-net-config: | |
| status: | In Progress → Fix Released |
Fix proposed to branch: stable/rocky
Review: https:/
Fix proposed to branch: stable/queens
Review: https:/
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 6252d770baa55ca
Author: Dan Sneddon <email address hidden>
Date: Sat Sep 29 04:28:14 2018 -0700
Apply IP/netmask/
Modifications to impl_ifcfg.py to support making changes to IP
address, MTU, and routes live, rather than running ifdown/ifup on the
interface. Bouncing the interface is very disruptive, especially with
bridges where all the child interfaces are also bounced.
If only the IP address, netmask, MTU, routes, and/or boot status are
changed, the file will be written and 'ip' or 'ip route' commands
will be run to apply the new config on the fly. If any commands fail,
the interface will be restarted instead.
Closes-bug: 1795129
Change-Id: I75239fd3f273a8
(cherry picked from commit c9bf347a238d450
| tags: | added: in-stable-rocky |
| tags: | added: in-stable-queens |
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit d3a0291e39b1ff9
Author: Dan Sneddon <email address hidden>
Date: Sat Sep 29 04:28:14 2018 -0700
Apply IP/netmask/
Modifications to impl_ifcfg.py to support making changes to IP
address, MTU, and routes live, rather than running ifdown/ifup on the
interface. Bouncing the interface is very disruptive, especially with
bridges where all the child interfaces are also bounced.
If only the IP address, netmask, MTU, routes, and/or boot status are
changed, the file will be written and 'ip' or 'ip route' commands
will be run to apply the new config on the fly. If any commands fail,
the interface will be restarted instead.
Closes-bug: 1795129
Change-Id: I75239fd3f273a8
(cherry picked from commit c9bf347a238d450
This issue was fixed in the openstack/
This issue was fixed in the openstack/
This issue was fixed in the openstack/
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit c9bf347a238d450
Author: Dan Sneddon <email address hidden>
Date: Sat Sep 29 04:28:14 2018 -0700
Apply IP/netmask/
Modifications to impl_ifcfg.py to support making changes to IP
address, MTU, and routes live, rather than running ifdown/ifup on the
interface. Bouncing the interface is very disruptive, especially with
bridges where all the child interfaces are also bounced.
If only the IP address, netmask, MTU, routes, and/or boot status are
changed, the file will be written and 'ip' or 'ip route' commands
will be run to apply the new config on the fly. If any commands fail,
the interface will be restarted instead.
Closes-bug: 1795129
Change-Id: I75239fd3f273a8