From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: [pve-devel] applied: [RFC PATCH 1/2] frr: add networking.service as systemd dependency
Date: Tue, 29 Jul 2025 14:26:18 +0200 [thread overview]
Message-ID: <175379195826.2310664.2782730309600173968.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250626131213.602226-1-g.goller@proxmox.com>
On Thu, 26 Jun 2025 15:12:12 +0200, Gabriel Goller wrote:
> Add networking.service to the 'After' dependency directive. Guarantees that
> the frr.service will start after the networking.service is done.
>
> We had some issues with data races between FRR and ifupdown [0], mostly
> around the dummy interface. At startup, FRR and by extension fabricd is
> up faster than the dummy interface which means that the interface won't
> be configured properly. This does not happen with 10.3.1 anymore due to
> this patch [1], which fixes the problem in the fabricd daemon.
>
> [...]
Applied, thanks!
[1/2] frr: add networking.service as systemd dependency
commit: 84509be6283fb93c638bab0e958f275cd57a7171
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-29 12:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 13:12 [pve-devel] " Gabriel Goller
2025-06-26 13:12 ` [pve-devel] [RFC PATCH 2/2] debian: bump version Gabriel Goller
2025-07-24 15:07 ` [pve-devel] [RFC PATCH 1/2] frr: add networking.service as systemd dependency Gabriel Goller
2025-07-29 12:26 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175379195826.2310664.2782730309600173968.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.