DLPX-79034 systemd-networkd releases its DHCP lease on restart #358
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses an issue that was introduced with the new version of systemd-networkd in Ubuntu 20.04, which is that when systemd-networkd stops (which happens when it restarts as part of applying an updated network configuration, for example), it releases its DHCP lease. A new lease is acquired when systemd-networkd starts again, but this leaves a window where the system has no IP address nor routes (those that were tied to the DHCP lease).
The fix is to configure systemd-networkd not to drop the lease on stop. A lease can be explicitly dropped by deleting a DHCP address (the only time when a lease should be dropped...).
This bug was responsible for the multitudes of dx-test failures documented in https://delphix.atlassian.net/browse/TOOL-12800, and there's a comment in that bug describing the RCA that lead to this bug fix.
ab-pre-push: http://selfservice.jenkins.delphix.com/job/appliance-build-orchestrator-pre-push/695/