From 0b961bc063f5fe8d4b32de2be82b511eabd7771a Mon Sep 17 00:00:00 2001 From: Christoph Heiss Date: Tue, 19 Nov 2024 16:13:44 +0100 Subject: [PATCH] first-boot: multi-user: start after product-specific API proxy First of, multi-user.target does not seem to really provide any (strong) ordering guarantee, it seems. Instead, let the "fully-up" ordering from the auto-installer depend on the product-specific API proxy instead. That way, it is ensured that 1) the system really is fully up and 2) that users could even use the API / CLI commands, or write files to pmxcfs (in case of PVE). After= and Wants= ignore non-existent units, so we can just specify all three API proxy units here w/o any conditional. Suggested-by: Shannon Sterz Signed-off-by: Christoph Heiss --- proxmox-first-boot/etc/proxmox-first-boot-multi-user.service | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service b/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service index d3c798d..a99d826 100644 --- a/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service +++ b/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service @@ -1,6 +1,7 @@ [Unit] Description=Proxmox First Boot Setup (Fully Booted) -After=systemd-remount-fs.service +After=systemd-remount-fs.service pveproxy.service pmgproxy.service proxmox-backup-proxy.service +Wants=pveproxy.service pmgproxy.service proxmox-backup-proxy.service ConditionPathExists=/var/lib/proxmox-first-boot/pending-first-boot-setup ConditionPathIsReadWrite=/var/lib