Open jmbaur opened 1 month ago
So one thing I did notice while implementing the rust switch-to-configuration is that the ability for the perl switch-to-configuration to report failed units is flawed. It is flawed in the sense that it only checks for units that have failed from the time that the script started/restarted/reloaded units, to the time it queries systemd for failed units. This means that if a unit fails further down the line, even if just a duration after the query, then the failure will not be reported. I left a note about this here. I am interested to know, is the current behavior actually preferred? The fact of there being a failed unit and going unnoticed seems tough.
Describe the bug
@nyabinary reported that the new (opt-in) switch-to-configuration implementation reported
systemd-networkd-wait-online.service
as failed while the perl implementation did not. Output below:Steps To Reproduce
Steps to reproduce the behavior:
networking.useNetworkd
andsystem.switch.enableNg
Expected behavior
Both implementations are consistent with one another.
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a :+1: reaction to issues you find important.