From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Gabriel Goller <g.goller@proxmox.com>
Subject: [pve-devel] applied: [PATCH manager] sdn: remove fabrics property correctly from EVPN controller
Date: Fri, 5 Sep 2025 21:07:14 +0200 [thread overview]
Message-ID: <175709923497.1470363.7711043916214801622.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250821085015.29401-1-g.goller@proxmox.com>
On Thu, 21 Aug 2025 10:50:06 +0200, Gabriel Goller wrote:
> The missing `deleteEmtpy` attribute caused the fabric property to never
> be removed from the EVPN controller. So when e.g. removing the fabric to
> add the peers manually, there would always be an error because you can't
> have peers *and* fabrics configured.
>
>
Applied, thanks!
[1/1] sdn: remove fabrics property correctly from EVPN controller
commit: 146cb84d7ca65016d2d1a1e427e659ec769d0a95
_______________________________________________
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-09-05 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 8:50 [pve-devel] " Gabriel Goller
2025-09-05 19:07 ` 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=175709923497.1470363.7711043916214801622.b4-ty@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