46d12ae7d3
NetworkManager takes a distinctly differnet network management approach and the bulk of the dhcp-all-interfaces code is largely targetted at distribution specific configuration. Some which may or may not override settings, or only partially assert desirable settings. As such, we need to set appropriate configuration, such as the correct client to be used, and timeouts based upon user supplied settings. By default this change sets the client to be dhclient on redhat styled machines, as the packaging default, while it works for ramdisk usage, it does not reset the interface between retries, which can be critical if the infrastucture operator is attempting to configure LACP trunks to the end node. Change-Id: I0e0cfbdbf7ef2b2861b934ccd7dab9d83a35c8f0 Story: 2008001 Task: 40648
10 lines
444 B
YAML
10 lines
444 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes support for the ``dhcp-all-interfaces`` element when the system
|
|
networking configuration is managed via ``NetworkManager``.
|
|
- |
|
|
Fixes ``NetworkManager`` configuration with the ``dhcp-all-interfaces``
|
|
element to account for Centos8/RHEL8's default change to the
|
|
``NetworkManager`` internal DHCP client, which can introduce different
|
|
behavior for infrastucture operators such as those using LACP.
|