From e0df22e7ce3637350515a59382f413926a38823f Mon Sep 17 00:00:00 2001 From: Prachi Agrawal Date: Wed, 5 Aug 2026 10:47:55 +0530 Subject: [PATCH] systemd: order update-engine after network-online.target update-engine.service currently starts and can mark a newly-updated partition as successful (~1 minute post-reboot) with no dependency on network availability. If a regression leaves the instance without network access, recovery today requires manual intervention via the serial console instead of an automatic rollback. Add After=/Wants=network-online.target so update-engine only starts once network-online.target has been reached. Uses Wants= rather than the Requires= suggested in the issue: systemd.special(7) specifically warns against Requires= on network-online.target, since it would stop update-engine outright if that target were ever deactivated, rather than simply deferring startup. Wants=+After= gives the same ordering without that failure mode. Fixes flatcar/Flatcar#521 Signed-off-by: Prachi Agrawal --- systemd/update-engine.service | 2 ++ 1 file changed, 2 insertions(+) diff --git a/systemd/update-engine.service b/systemd/update-engine.service index e2ac3a8..4bd8f81 100644 --- a/systemd/update-engine.service +++ b/systemd/update-engine.service @@ -2,6 +2,8 @@ Description=Update Engine ConditionVirtualization=!container ConditionPathExists=!/usr/.noupdate +After=network-online.target +Wants=network-online.target [Service] Type=dbus