Re: [pve-devel] [PATCH frr 0/2] Bump FRR to 10.4.1

["DERUMIER, Alexandre via pve-devel" <pve-devel@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 15823 bytes --]

From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH frr 0/2] Bump FRR to 10.4.1
Date: Tue, 25 Nov 2025 16:53:06 +0000
Message-ID: <303fec039b8faa7ae3b78e3872e142e4ff304dcb.camel@groupe-cyllene.com>

Hi, 

10.4.2 has been released last week.


be carefull with frr updates, from my experience they are always to a
lot of bugs && regression when new major version is release,
and sometime it take weeks to triggers specific bugs in production.
(and even more to debug)

and frr still maintain 10.2 branch for example (10.2.5).


Personnaly, for my pve9 production, I'll pin my frr version to 10.2,
because I don't have time to retest new version each 6 months.



-------- Message initial --------
De: Gabriel Goller <g.goller@proxmox.com>
Répondre à: Proxmox VE development discussion <pve-
devel@lists.proxmox.com>
À: pve-devel@lists.proxmox.com
Objet: [pve-devel] [PATCH frr 0/2] Bump FRR to 10.4.1
Date: 21/11/2025 15:13:21

Bump FRR to 10.4.1, we do this for two reasons:
 * we can drop two patches, which have been merged upstream
 * fix the libyang errors in the journal
 * try to update a bit more frequently (maybe always one minor version
behind
   upstream would be nice), so that we can avoid the fallout of
updating two
   major versions (8->10) again.

Went through the changelog quite thoroughly, didn't find anything that
could
cause an issue. Tested it on a few clusters I had lying around (ospf,
fabricd(ip4 and ip6), bgp+evpn) and didn't notice anything off. Stefan
said
he'd test on his clusters next week as well. Would be nice if we get it
in
early so that we have a nice long testing period.

frr:

Gabriel Goller (2):
  bump frr to 10.4.1, remove obsolete patches
  d/changelog: bump package version

 debian/changelog                              |   6 +
 ...ummy_as_loopback-option-per-default.patch} |   0
 ...A_IF_DUMMY-flag-for-dummy-interfaces.patch | 125 -----------
 ...on-to-treat-dummy-interfaces-as-loop.patch | 206 ------------------
 ...dd-dependancy-to-networking.service.patch} |   0
 ...-starting-order-for-debian-packages.patch} |   0
 debian/patches/series                         |   8 +-
 frr                                           |   2 +-
 8 files changed, 10 insertions(+), 337 deletions(-)
 rename debian/patches/pve/{0006-fabricd-enable-dummy_as_loopback-
option-per-default.patch => 0004-fabricd-enable-dummy_as_loopback-
option-per-default.patch} (100%)
 delete mode 100644 debian/patches/pve/0004-zebra-add-ZEBRA_IF_DUMMY-
flag-for-dummy-interfaces.patch
 delete mode 100644 debian/patches/pve/0005-fabricd-add-option-to-
treat-dummy-interfaces-as-loop.patch
 rename debian/patches/pve/{0007-systemd-add-dependancy-to-
networking.service.patch => 0005-systemd-add-dependancy-to-
networking.service.patch} (100%)
 rename debian/patches/pve/{0007-tools-fix-daemon-starting-order-for-
debian-packages.patch => 0006-tools-fix-daemon-starting-order-for-
debian-packages.patch} (100%)


Summary over all repositories:
  8 files changed, 10 insertions(+), 337 deletions(-)


[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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