hl-fwdesk: ignore hermes VM fabric links in networkd wait-online
systemd-networkd-wait-online fails on every boot of hl-fwdesk with "Timeout occurred while waiting for network connectivity" and status=1/FAILURE. The hermes VM runs on this host via services.hermenix (ari/hermenix flake input), and its fabric interfaces -- the bridge hermes-br and the tap vm-hermes -- are managed by systemd-networkd (10-hermes-br.network, 11-vm-hermes.network). networkd-managed links default to RequiredForOnline=yes, but those two links only gain carrier when the VM starts, which on the sampled boot was 0.2s after the 120s wait-online timeout fired. The only networkd link that never blocks is robotnix's own bridge, and the physical uplink enp191s0 is owned by NetworkManager, so it is invisible to networkd. The result is a unit that always burns the full timeout and then fails. hermenix now passes --ignore=hermes-br --ignore=vm-hermes to the unit, so it no longer treats the VM's fabric links as a condition for "online": with every candidate ignored the wait returns immediately instead of blocking and then failing. The unit itself stays enabled and anyInterface is untouched. The durable fix belongs in ari/hermenix: set RequiredForOnline = "no" on the hermes-br and vm-hermes .network files, the same way modules/nixos/server/robotnix/network.nix already does for the robotnix fabric. That repository is out of scope for this change; once it lands this ignoredInterfaces entry can be dropped. Found by hermenix from the fleet monitor's persistent failure record for unit:hub:systemd-networkd-wait-online.service.
This commit is contained in:
1 parent
eb6380ddfe
commit
57fbf70b7c
1 file changed
+5
@@ -1,4 +1,9 @@
|
||||
{ ... }:
|
||||
{
|
||||
services.tailscale.enable = true;
|
||||
|
||||
systemd.network.wait-online.ignoredInterfaces = [
|
||||
"hermes-br"
|
||||
"vm-hermes"
|
||||
];
|
||||
}
|
||||
Reference in new issue
Block a user