https://github.com/vyos/vyos-1x/pull/2032

Found the problem with command:

Could you please try the configuration in the latest rolling release.

In this case I found the ipv6-address-group and ipv6-network-group not assigned without name or group. Because it's can't show references.

PR: https://github.com/vyos/vyos-1x/pull/2027

PR https://github.com/vyos/vyos-build/pull/356
PR https://github.com/vyos/vyos-1x/pull/2033

PR:
https://github.com/vyos/vyos-1x/pull/2026

PR for vyos-1x https://github.com/vyos/vyos-1x/pull/2025

Maybe related with https://vyos.dev/T5048

PR https://github.com/vyos/vyos-build/pull/355

Draft PR re-opened following fix of regression with option 'recursive'; simplified logic and added optional args to get_config_defaults to mirror get_config_dict. The latter allows easy manipulation of defaults in cases where the automatic merge is not sufficient.

There are no network or broadcast addresses in v6 like there are in v4. The first address (ex: 2a10:ffff:ffff::/64) is the Anycast address for "All Routers" on a subnet in v6 land.

Well, in an example like yours, using the network address as an IP is not really best practice even tho its works.
So, the validator forces the users to do it the right way, which is probably a good thing.

Validator doesn't allow setting network address to the interface
the same way you can't add 10.2.3.0/24 to interface
But natively it seems working

vyos@r14# sudo ip a add 10.5.0.0/24 dev eth0
[edit]
vyos@r14# ping 10.5.0.0
PING 10.5.0.0 (10.5.0.0) 56(84) bytes of data.
64 bytes from 10.5.0.0: icmp_seq=1 ttl=64 time=0.062 ms
^C

This did solve it. I did not search thoroughly enough it seems.

this issues was resolved on https://vyos.dev/T5127. It happens when FRR tries to calculate the auto-rd per vrf . it can be solved by using router-id on each vrf or interface dummy in the VRFs ,

Chiming in here as a 'me too', on vyos-1.4-rolling-202305300317

PR's:
https://github.com/vyos/libvyosconfig/pull/11 (merged)
https://github.com/vyos/vyos-1x/pull/2023