* [pve-devel] [PATCH installer] first-boot: multi-user: start after pveproxy.service
@ 2024-11-19 14:39 Christoph Heiss
2024-11-19 14:50 ` Thomas Lamprecht
0 siblings, 1 reply; 3+ messages in thread
From: Christoph Heiss @ 2024-11-19 14:39 UTC (permalink / raw)
To: pve-devel
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
pveproxy.service 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.
Suggested-by: Shannon Sterz <s.sterz@proxmox.com>
Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
---
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..4b30e7e 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
+Wants=pveproxy.service
ConditionPathExists=/var/lib/proxmox-first-boot/pending-first-boot-setup
ConditionPathIsReadWrite=/var/lib
--
2.47.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [pve-devel] [PATCH installer] first-boot: multi-user: start after pveproxy.service
2024-11-19 14:39 [pve-devel] [PATCH installer] first-boot: multi-user: start after pveproxy.service Christoph Heiss
@ 2024-11-19 14:50 ` Thomas Lamprecht
2024-11-19 15:03 ` Christoph Heiss
0 siblings, 1 reply; 3+ messages in thread
From: Thomas Lamprecht @ 2024-11-19 14:50 UTC (permalink / raw)
To: Proxmox VE development discussion, Christoph Heiss
Am 19.11.24 um 15:39 schrieb Christoph Heiss:
> 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
> pveproxy.service 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.
>
> Suggested-by: Shannon Sterz <s.sterz@proxmox.com>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> 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..4b30e7e 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
> +Wants=pveproxy.service
do we already want to add the units of the API from our other products now
already?
> ConditionPathExists=/var/lib/proxmox-first-boot/pending-first-boot-setup
> ConditionPathIsReadWrite=/var/lib
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [pve-devel] [PATCH installer] first-boot: multi-user: start after pveproxy.service
2024-11-19 14:50 ` Thomas Lamprecht
@ 2024-11-19 15:03 ` Christoph Heiss
0 siblings, 0 replies; 3+ messages in thread
From: Christoph Heiss @ 2024-11-19 15:03 UTC (permalink / raw)
To: Thomas Lamprecht; +Cc: Proxmox VE development discussion
On Tue, Nov 19, 2024 at 03:50:47PM +0100, Thomas Lamprecht wrote:
> Am 19.11.24 um 15:39 schrieb Christoph Heiss:
> > [..]
> > 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..4b30e7e 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
> > +Wants=pveproxy.service
>
> do we already want to add the units of the API from our other products now
> already?
Right, was a bit to quick for my own good with this.
Makes sense, I'll test that and send a v2 shortly.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-11-19 15:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-11-19 14:39 [pve-devel] [PATCH installer] first-boot: multi-user: start after pveproxy.service Christoph Heiss
2024-11-19 14:50 ` Thomas Lamprecht
2024-11-19 15:03 ` Christoph Heiss
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox