-
Notifications
You must be signed in to change notification settings - Fork 63
fix(lib): write drop-in configs to active network file directory #147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mjnowen
wants to merge
1
commit into
amazonlinux:main
Choose a base branch
from
mjnowen:fix/dropin-dir-follows-active-network-file
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could there be a race condition between netplan and ec2-net-utils during a restart where netplan config is not first and you have two seperate configs since netplan has not logic to append to ec2-net-utils config?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
policy-routes@.servicestartpath callssystemd-networkd-wait-online -i $ifacebefore_get_active_dropin_dir()is ever invoked, so networkd has already selected its active.networkfile (including any netplan-generated one) by that time. Therefreshpath (timer-driven) does not callwait-onlineexplicitly, but the timer only fires 30s+ after thestartpath completes (OnActiveSec=30,OnUnitInactiveSec=60), so the interface is already fully online andNETWORK_FILE=is populated.On Ubuntu, netplan's systemd generator runs during the early generator phase — before any services start — so
10-netplan-*.networkfiles are on disk well beforesystemd-networkd.servicebegins matching interfaces to files.On Amazon Linux 2023 there is no competing generator —
70-<iface>.networkis the only (and therefore active) file, so the helper returns the same path as the old hardcoded logic and no race is possible.On RHEL the default network manager is NetworkManager rather than systemd-networkd, so this codepath does not apply.
If detection somehow fails (e.g. a truly degenerate early-boot ordering), the helper falls back to
70-<iface>.network.d— the same path used before this change — so the worst case is parity with the current behaviour, not a new failure mode.The coexistence of
70-<iface>.networkalongside a lower-numbered netplan file is pre-existing and unchanged by this PR; it's precisely that coexistence that causes the bug this fix addresses.