-
Notifications
You must be signed in to change notification settings - Fork 201
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
Migrate CriticalConnection (deprecated) to KeepConfiguration (LP: #1896799) #424
Conversation
@chr4 Are you OK with getting this landed first before we continue with the extension of The extension requires some consensus on new Netplan YAML schema, so it takes a bit longer, but the few lines from this PR should already fix the issue, while providing a (limited) KeepConfiguration= setting. Let me know what you think! PS: I attributed the changes to your name. |
No issues with taking the long road here, I agree that this is more consistent (and solves a few issues that came up in the discussion of #409).
Thanks, much apprechiated! |
@@ -482,7 +482,7 @@ def test_dhcp_critical_true(self): | |||
LinkLocalAddressing=ipv6 | |||
|
|||
[DHCP] | |||
CriticalConnection=true | |||
KeepConfiguration=true |
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.
They put it into Network section, though it still modifies DHCPv4 behaviour.
DHCP.CriticalConnection / DHCPv4.CriticalConnection => Network.KeepConfiguration
https://www.freedesktop.org/software/systemd/man/latest/systemd.network.html#KeepConfiguration=
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.
Very good catch, thanks a lot! Fixed in 76e896a
Description
With systemd-v243 (which is the default since focal), the "CriticalConnection" attribute was
revamped into "KeepConfiguration" [1], addressing several issues, especially in high-availability
environents [2][3].
This PR is preparatory work for #409
If I understand the code correctly, it still uses "CriticalConnection" when setting "critical: true" in the netplan configuration.
Closes: https://bugs.launchpad.net/netplan/+bug/1896799
Checklist
make check
successfully.make check-coverage
).