Migrate deprecated "CriticalConnection" attribute to "KeepConfiguration" (systemd-networkd)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Triaged
|
Medium
|
Unassigned |
Bug Description
With systemd-v243 (which is the default since focal), the "CriticalConnec
revamped into "KeepConfiguration" [1], addressing several issues, especially in high-availability
environents [2][3].
The new "KeepConfiguration" setting can take multiple arguments, according to the documentation
[4]:
> Takes a boolean or one of "static", "dhcp-on-stop", "dhcp". When "static", systemd-networkd will
> not drop static addresses and routes on starting up process. When set to "dhcp-on-stop",
> systemd-networkd will not drop addresses and routes on stopping the daemon. When "dhcp", the
> addresses and routes provided by a DHCP server will never be dropped even if the DHCP lease
> expires. This is contrary to the DHCP specification, but may be the best choice if, e.g., the
> root filesystem relies on this connection. The setting "dhcp" implies "dhcp-on-stop", and "yes"
> implies "dhcp" and "static". Defaults to "no".
If I understand the code correctly, it still uses "CriticalConnec
- [1] https:/
- [2] https:/
- [3] https:/
- [4] https:/
I could dedicate some time working working on this if help is wanted.
Thanks for your report, pull requests are always welcome!
This might also be related to: https:/ /bugs.launchpad .net/netplan/ +bug/1815101