From f2ed4d4829629a7a17499c7cd5949275df0913f7 Mon Sep 17 00:00:00 2001 From: Konstantin Renner Date: Thu, 2 Jul 2026 16:10:44 +0200 Subject: [PATCH] =?UTF-8?q?edge-host:=20drop=20CAN=20RestartSec=20?= =?UTF-8?q?=E2=80=94=20gs=5Fusb=20can't=20bus-off-restart?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit networkd fails the entire can0 configuration on the unsupported option ("Device doesn't support restart from Bus Off") and never raises the link — found by the reboot test; this, not a socket race, was also the afternoon's "off (failed)". Bus-off recovery falls to open3e's service restart loop. Co-Authored-By: Claude Fable 5 --- ansible/roles/edge-host/templates/80-can0.network.j2 | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/ansible/roles/edge-host/templates/80-can0.network.j2 b/ansible/roles/edge-host/templates/80-can0.network.j2 index b091154a..246dd95f 100644 --- a/ansible/roles/edge-host/templates/80-can0.network.j2 +++ b/ansible/roles/edge-host/templates/80-can0.network.j2 @@ -11,5 +11,7 @@ ActivationPolicy=always-up [CAN] BitRate={{ edge_can_bitrate }} -# Auto-recover the link if the controller ever goes bus-off. -RestartSec=1s +# NO RestartSec here: gs_usb does not support hardware bus-off restart, +# and networkd fails the ENTIRE link configuration on the unsupported +# option ("off (failed)", link never raised — found by reboot test). +# Bus-off recovery falls to the open3e service restart loop. -- 2.54.0