h21/HoralOS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Configure Azure DHCP to retry indefinitely

Browse Source 
Azure requires VMs to attempt DHCP for at least 300 seconds during
provisioning. Setting ipv4.dhcp-timeout and ipv6.dhcp-timeout to
2147483647 (NetworkManager's value for infinity) allows indefinite
retries, which is robust than fixed timeout value. Both IPv4 and IPv6
are configured to prepare for IPv6-only scenarios.

Signed-off-by: Bala Konda Reddy M <bala12352@gmail.com>
This commit is contained in:
Bala Konda Reddy M
2026-01-22 12:03:05 -08:00
parent 89f990af38
commit bb62046d42
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
config.sh
+14
View File
@@ -180,6 +180,20 @@ cat > /etc/NetworkManager/conf.d/99-azure-unmanaged-devices.conf << EOF
[keyfile]
unmanaged-devices=driver:mlx4_core;driver:mlx5_core
EOF
# Configure DHCP timeout for Azure to retry indefinitely during VM provisioning
cat > /etc/NetworkManager/conf.d/99-azure-dhcp-timeout.conf << EOF
# Azure requires VMs to attempt DHCP for at least 300 seconds during provisioning,
# as that's the upper bound of how long Azure waits to make networking available.
# NetworkManager's ipv4.dhcp-timeout setting accepts 2147483647 as a special value
# representing infinity, which ensures DHCP keeps retrying indefinitely. This is
# more robust than a fixed timeout and matches systemd-networkd's default behavior.
# Both IPv4 and IPv6 are configured to prepare for IPv6-only scenarios.
# Reference: https://networkmanager.dev/docs/api/latest/nm-settings-nmcli.html
[connection]
ipv4.dhcp-timeout=2147483647
ipv6.dhcp-timeout=2147483647
EOF
fi
if [[ "$kiwi_profiles" == *"GCE"* ]]; then