From: Hannes Laimer <h.laimer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: superseded: [PATCH pve-network] sdn: frr: add bgpd to SDN-managed daemons
Date: Tue, 19 May 2026 11:26:17 +0200 [thread overview]
Message-ID: <c3a1b5d5-3d32-4bd2-a1e7-35b223205fe0@proxmox.com> (raw)
In-Reply-To: <20260519081752.15175-1-h.laimer@proxmox.com>
superseded-by:
https://lore.proxmox.com/pve-devel/20260519092537.19326-1-h.laimer@proxmox.com/T/#u
On 2026-05-19 10:18, Hannes Laimer wrote:
> Every sdn-apply on a node that has a BGP fabric configured trips the
> set_daemon_status() guard with "bgpd is not SDN managed", aborting FRR
> config generation. The Rust enabled_daemons() reports bgpd for BGP
> fabrics, but the Perl allowlist was only updated for OSPF and OpenFabric
> when those fabric types were originally added.
>
> Fixes: 9d8533d ("sdn: fabrics: register bgp as a fabric protocol type")
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
> src/PVE/Network/SDN/Frr.pm | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/PVE/Network/SDN/Frr.pm b/src/PVE/Network/SDN/Frr.pm
> index 7c60d28..642610c 100644
> --- a/src/PVE/Network/SDN/Frr.pm
> +++ b/src/PVE/Network/SDN/Frr.pm
> @@ -125,6 +125,7 @@ sub restart {
> my $SDN_DAEMONS_DEFAULT = {
> ospfd => 0,
> fabricd => 0,
> + bgpd => 0,
> };
>
> =head3 set_daemon_status(\%daemons, $set_default)
prev parent reply other threads:[~2026-05-19 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 8:17 [PATCH pve-network] sdn: frr: add bgpd to SDN-managed daemons Hannes Laimer
2026-05-19 8:54 ` Gabriel Goller
2026-05-19 9:20 ` Hannes Laimer
2026-05-19 9:26 ` Hannes Laimer [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=c3a1b5d5-3d32-4bd2-a1e7-35b223205fe0@proxmox.com \
--to=h.laimer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox