From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id C3D9D1FF16F
	for <inbox@lore.proxmox.com>; Tue, 15 Apr 2025 12:23:36 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id F3E7A4807;
	Tue, 15 Apr 2025 12:23:35 +0200 (CEST)
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Tue, 15 Apr 2025 12:23:00 +0200
Message-Id: <20250415102301.848940-1-s.hanreich@proxmox.com>
X-Mailer: git-send-email 2.39.5
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.233 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
 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery
 methods
 RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_NONE                0.001 SPF: sender does not publish an SPF Record
Subject: [pve-devel] [PATCH frr 1/2] update to 10.2.2
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

When rebooting single nodes, BFD is not always able to re-establish
its sessions, as reported by users in our forum [1] [2]. The
corresponding FRR issue seems to be found in [3].

The issue mainly surfaced when updating nodes one-by-one and then
rebooting, leading some hosts to not be able to re-establish the BFD
session which leads to the BGP session being stuck in Idle.

[1] https://forum.proxmox.com/threads/networking-somewhat-broken-after-upgrade-bfd-bgp.165055/
[2] https://forum.proxmox.com/threads/evpn-vxlan-transport-endpoint-is-not-connected-after-node-takedown-and-rejoin-sdn.165021/
[3] https://github.com/FRRouting/frr/issues/17751

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 frr | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/frr b/frr
index 5f0beaa..e3b6a8c 160000
--- a/frr
+++ b/frr
@@ -1 +1 @@
-Subproject commit 5f0beaa0fdd00b7a60c1765067d1b6fa65ce96c0
+Subproject commit e3b6a8c459399e39cce81bed8ff75f60da88b0a3
-- 
2.39.5


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel