all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-network v2] sdn: frr: add bgpd to SDN-managed daemons
Date: Tue, 19 May 2026 14:06:21 +0200	[thread overview]
Message-ID: <59190ec5-5dea-49c5-8fe3-c52351d5a407@proxmox.com> (raw)
In-Reply-To: <20260519092537.19326-1-h.laimer@proxmox.com>

On 5/19/26 11:25 AM, 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.
> 
> Default bgpd to enabled, unlike ospfd and fabricd: the BGP and EVPN
> controllers also depend on bgpd and do not manage /etc/frr/daemons
> themselves, so removing the last BGP fabric must not silently disable
> bgpd on a system where a controller still needs it.
> 
> Fixes: 9d8533d ("sdn: fabrics: register bgp as a fabric protocol type")
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---

Just ran into this while testing and can confirm this fixes the SDN 
network reload on apply. FWIW, consider:

Tested-by: Christian Ebner <c.ebner@proxmox.com>




      parent reply	other threads:[~2026-05-19 12:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  9:25 [PATCH pve-network v2] sdn: frr: add bgpd to SDN-managed daemons Hannes Laimer
2026-05-19 10:45 ` Gabriel Goller
2026-05-19 12:06 ` Christian Ebner [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=59190ec5-5dea-49c5-8fe3-c52351d5a407@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal