From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 9BF2E1FF13B for ; Wed, 20 May 2026 13:26:29 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 818952FD7; Wed, 20 May 2026 13:26:28 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH pve-network v2] sdn: frr: add bgpd to SDN-managed daemons Date: Wed, 20 May 2026 13:25:44 +0200 Message-ID: <177927634239.171689.11688598314167297997.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260519092537.19326-1-h.laimer@proxmox.com> References: <20260519092537.19326-1-h.laimer@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779276339014 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.004 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 3CM2Z2UYR46ZCLSY24FQMBT4YNEGJI5U X-Message-ID-Hash: 3CM2Z2UYR46ZCLSY24FQMBT4YNEGJI5U X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Tue, 19 May 2026 11:25:37 +0200, 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. > > [...] Applied, thanks! [1/1] sdn: frr: add bgpd to SDN-managed daemons commit: 9cc7f9b99281bfd303d185a6d43950dba5140dd7