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 <s.sterz@proxmox.com>
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
This commit is contained in:
Christoph Heiss 2024-11-19 16:13:44 +01:00 committed by Thomas Lamprecht
parent fa97aeb1f5
commit 0b961bc063

View File

@ -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