6d64a2aee6
In Ubuntu/Debian, the default dependencies cannot be relied upon as we enter into a cyclical dependency relationship which prevents the unit from starting. Added the required configuration to the systemd unit file. This issue has also been observed in glean[0], which has a nearly identical unit file for interface start-up. [0]: https://review.openstack.org/#/c/485748 Closes-Bug: #1708685 Change-Id: I23ac9510d1a21c7073bd33f76ba66fa04a8be035 |
||
|---|---|---|
| .. | ||
| install.d | ||
| element-deps | ||
| package-installs.yaml | ||
| pkg-map | ||
| README.rst | ||
dhcp-all-interfaces
Autodetect network interfaces during boot and configure them for DHCP
The rationale for this is that we are likely to require multiple network interfaces for use cases such as baremetal and there is no way to know ahead of time which one is which, so we will simply run a DHCP client on all interfaces with real MAC addresses (except lo) that are visible on the first boot.
On non-Gentoo based distributions the script /usr/local/sbin/dhcp-all-interfaces.sh will be called early in each boot and will scan available network interfaces and ensure they are configured properly before networking services are started.
On Gentoo based distributions we will install the dhcpcd package and ensure the service starts at boot. This service automatically sets up all interfaces found via dhcp and/or dhcpv6 (or SLAAC).
Environment Variables
- DIB_DHCP_TIMEOUT
-
- Required
-
No
- Default
-
30
- Description
-
Amount of time in seconds that the systemd service will wait to get an address.
- Example
-
DIB_DHCP_TIMEOUT=300