From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Gabriel Goller <g.goller@proxmox.com>
Subject: [pve-devel] applied: [PATCH network] frr: update frr version in config file
Date: Wed, 10 Dec 2025 20:32:17 +0100 [thread overview]
Message-ID: <3657ecbe-461a-49e6-8a29-191b41ae8e61@proxmox.com> (raw)
In-Reply-To: <20251209105731.19965-1-g.goller@proxmox.com>
Am 09.12.25 um 11:57 schrieb Gabriel Goller:
> Frr recently got updated to 10.4.1. Update the config generation so that
> the config file correctly reads "frr version 10.4.1". Also updated the
> tests.
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
> src/PVE/Network/SDN/Frr.pm | 2 +-
> .../zones/evpn/advertise_subnets/expected_controller_config | 2 +-
> .../evpn/disable_arp_nd_suppression/expected_controller_config | 2 +-
> src/test/zones/evpn/ebgp/expected_controller_config | 2 +-
> src/test/zones/evpn/ebgp_loopback/expected_controller_config | 2 +-
> src/test/zones/evpn/exitnode/expected_controller_config | 2 +-
> .../evpn/exitnode_local_routing/expected_controller_config | 2 +-
> src/test/zones/evpn/exitnode_primary/expected_controller_config | 2 +-
> src/test/zones/evpn/exitnode_snat/expected_controller_config | 2 +-
> .../zones/evpn/exitnodenullroute/expected_controller_config | 2 +-
> src/test/zones/evpn/ipv4/expected_controller_config | 2 +-
> src/test/zones/evpn/ipv4ipv6/expected_controller_config | 2 +-
> .../zones/evpn/ipv4ipv6nogateway/expected_controller_config | 2 +-
> src/test/zones/evpn/ipv6/expected_controller_config | 2 +-
> src/test/zones/evpn/ipv6underlay/expected_controller_config | 2 +-
> src/test/zones/evpn/isis/expected_controller_config | 2 +-
> src/test/zones/evpn/isis_loopback/expected_controller_config | 2 +-
> src/test/zones/evpn/isis_standalone/expected_controller_config | 2 +-
> src/test/zones/evpn/multipath_relax/expected_controller_config | 2 +-
> src/test/zones/evpn/multiplezones/expected_controller_config | 2 +-
> .../zones/evpn/openfabric_fabric/expected_controller_config | 2 +-
> src/test/zones/evpn/ospf_fabric/expected_controller_config | 2 +-
> src/test/zones/evpn/rt_import/expected_controller_config | 2 +-
> src/test/zones/evpn/vxlanport/expected_controller_config | 2 +-
> 24 files changed, 24 insertions(+), 24 deletions(-)
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-12-10 19:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 10:57 [pve-devel] " Gabriel Goller
2025-12-10 19:32 ` Thomas Lamprecht [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=3657ecbe-461a-49e6-8a29-191b41ae8e61@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=g.goller@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox