--- Begin Message ---
Hi,
sorry I didn't see your message and was super busy
>>Yeah, that's exactly why I want to release every minor FRR version
>>(while staying one release behind). This approach should minimize
>>the impact when a major version is released. The big issue with PVE
>>8.5 was jumping from FRR 8 to 10 -- that's two major versions at
>>once, which caused many problems. I believe it's better to do
>>frequent small updates where issues are discovered quickly, rather
>>than large yearly updates where many problems surface at once.
>>
>>What do you think about this?
Well, It's like ceph, you don't want uncontrolled major upgrade. (Minor
are ok, because they are only backporting small patches).
so , doing it during major PVE upgrade is ok. or adding a version
handling like ceph.
The only problem is that they don't have an LTS for security upgrade
This is a criticial part of infrastructure, even more criticial than
ceph
>>That said, I understand your concerns. We've also seen FRR being
>>quite unstable lately with many regressions in recent releases.
>>
>>>>
FRR updates always had regression, when I had implement evpn I had
regression with 7.5,7.6,7.8,8.0,8.1 as far I remember.
so, you really don't need to big gap to have problem, it's occur all
time (I don't known, they don't seem to have automatic test on readl
infra)
here we go again.... :/
https://forum.proxmox.com/threads/frr-update-to-10-4-1-1-broke-external-routing.177736/
>>The maintainers have told me this should improve going forward.
don't trust them ;)
-------- Message initial --------
De: Gabriel Goller <[email protected]>
À: Proxmox VE development discussion <[email protected]>
Cc: "DERUMIER, Alexandre" <[email protected]>,
Thomas Lamprecht <[email protected]>
Objet: Re: [pve-devel] [PATCH frr 0/2] Bump FRR to 10.4.1
Date: 26/11/2025 13:59:00
On 25.11.2025 16:53, DERUMIER, Alexandre via pve-devel wrote:
> Hi,
>
> 10.4.2 has been released last week.
I don't think so? At least I can't see the tag on github...
> 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)
Yeah, that's exactly why I want to release every minor FRR version
(while staying one release behind). This approach should minimize
the impact when a major version is released. The big issue with PVE
8.5 was jumping from FRR 8 to 10 -- that's two major versions at
once, which caused many problems. I believe it's better to do
frequent small updates where issues are discovered quickly, rather
than large yearly updates where many problems surface at once.
What do you think about this?
That said, I understand your concerns. We've also seen FRR being
quite unstable lately with many regressions in recent releases. The
maintainers have told me this should improve going forward.
> 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.
Pinning is always possible and something the user can do. Maybe we
should create a official "guide" or article on how pin in case of
critical network bugs.
Obviously the newer features (e.g. fabrics) won't work.
I don't know how we handle other upstream dependencies that are
critical
yet optional? @Thomas?
Gabriel
--- End Message ---
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
