From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [RFC PATCH 1/2] frr: add networking.service as systemd dependency
Date: Thu, 24 Jul 2025 17:07:30 +0200 [thread overview]
Message-ID: <q5ksk6nodloz7y3rqfikl5gbqe5an2xydwejtnmzvtm62sgerv@3jwgsowcwscs> (raw)
In-Reply-To: <20250626131213.602226-1-g.goller@proxmox.com>
ping
Hannes and I tried to fix the errors that appear when starting FRR
10.3.1 (even on a blank config). The errors look similar to these:
Jul 22 08:36:09 pve1 zebra[845]: libyang Invalid boolean value "". (/frr-vrf:lib/vrf/state/active)
Jul 22 08:36:09 pve1 zebra[845]: libyang Invalid type uint32 empty value. (/frr-vrf:lib/vrf/state/id)
(and some other ones).
For us this is partially fixed with this patch (which we obviously can't
upstream because frr doesn't rely on systemd) and the following PR:
https://github.com/FRRouting/frr/pull/19248.
This patch can be applied already, it also fixes some other errors like
frr starting before the dummy interfaces are created.
I'd like to wait a bit for some feedback from the maintainers before
backporting the PR though, as that's quite a tricky change and I don't
know if it is correct.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-07-24 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 13:12 Gabriel Goller
2025-06-26 13:12 ` [pve-devel] [RFC PATCH 2/2] debian: bump version Gabriel Goller
2025-07-24 15:07 ` Gabriel Goller [this message]
2025-07-29 12:26 ` [pve-devel] applied: [RFC PATCH 1/2] frr: add networking.service as systemd dependency 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=q5ksk6nodloz7y3rqfikl5gbqe5an2xydwejtnmzvtm62sgerv@3jwgsowcwscs \
--to=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