Backport systemd patches and configure netlink timeout #3520
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.
Issue number:
N/A
Description of changes:
This PR backports a few patches from a recent
systemd
issue. Further details are in the issue; the tl;dr is that on a heavily loaded system (such as one running many containers/pods), it is possible for the kernel to not respond toRTM_NEWROUTE
requests within the current default 25 second timeout. This results in network links becoming unusable. Bottlerocket now sets this timeout toinfinity
since we require all links to be usable, especially the main link, even if the system is heavily loaded.Testing done:
systemd-networkd
's environment shows the appropriate variable after this change:Also set a super short timeout of
1ms
and watched the network fail to come up:Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.