From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH frr 0/4] revert frr to 7.4
Date: Sun, 22 Aug 2021 12:07:57 +0200 [thread overview]
Message-ID: <20210822100801.511588-1-aderumier@odiso.com> (raw)
frr 7.5.1 seem to be really buggy with evpn,
because of new the evpn multi-homing implementation.
I have already found 2 bugs, 1 is already fixed in frr 8.0,
but the other seem be racy and difficult to reproduce (was able to reproduce 3 times),
and not yet fixed in frr 8.0.
So until it's fixed, this patch series is reverting to 7.4,
with "7.5.1-99+pve~really7.4" version to be sure to have the priority over
debian package.
Alexandre Derumier (4):
Revert "update submodule to frr-7.5.1"
Revert "update patches"
fix python3.9
bump to 7.5.1-99+pve~really7.4
Makefile | 2 +-
debian/changelog | 7 ++++++
...e-ax_python.m4-to-hardcode-python3.9.patch | 25 +++++++++++++++++++
.../patches/pve/0001-enable-bgp-daemon.patch | 10 ++++----
...on-for-RT-auto-derivation-to-force-A.patch | 24 +++++++++---------
debian/patches/series | 1 +
frr | 2 +-
7 files changed, 52 insertions(+), 19 deletions(-)
create mode 100644 debian/patches/0001-Adjust-the-ax_python.m4-to-hardcode-python3.9.patch
--
2.30.2
next reply other threads:[~2021-08-22 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 10:07 Alexandre Derumier [this message]
2021-08-22 10:07 ` [pve-devel] [PATCH frr 1/4] Revert "update submodule to frr-7.5.1" Alexandre Derumier
2021-08-22 10:07 ` [pve-devel] [PATCH frr 2/4] Revert "update patches" Alexandre Derumier
2021-08-22 10:08 ` [pve-devel] [PATCH frr 3/4] fix python3.9 Alexandre Derumier
2021-08-22 10:08 ` [pve-devel] [PATCH frr 4/4] bump to 7.5.1-99+pve~really7.4 Alexandre Derumier
2021-08-24 8:47 ` [pve-devel] applied-series: Re: [PATCH frr 0/4] revert frr to 7.4 Thomas Lamprecht
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=20210822100801.511588-1-aderumier@odiso.com \
--to=aderumier@odiso.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