Oh, the problem still persists. I need someone to help, because I only get this error on a few infrastructures.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
All Stories
Jul 6 2025
Jul 5 2025
Jul 4 2025
Jul 3 2025
I found the cause. You need to mark which interface will run it.
Jul 2 2025
The Document was created in Confluence
good to know!
Confirmed working on 2025.07.01-0813-rolling, interfaces no longer appears in ra-interfaces after setting and resetting BGP
Jul 1 2025
Thanks, @yun , this is a known issue, as the sanitization functions have not yet been moved from the python module, for direct loads by vyconfd:
https://github.com/vyos/vyos-1x/blob/current/python/vyos/configtree.py#L38-L47
It's on the short term list to do.
I'll mention that, commonly, errors reporting on usr/bin/config-mgmt are the result of an earlier build error; scroll up on the output to see if anything else is reported.
I'll follow this up on the forum as that is probably a better place for this discussion but I followed those instructions verbatim on a brand new virtual machine install with fresh up to date docker images and it fails in the exact same way every time. Are you running on an old machine you've had set up for a long time? It might have state in it that allows builds that's not present on fresh installs.
Do not see any issues:
$ docker run --rm -it --privileged -v $(pwd):/vyos -w /vyos vyos/vyos-build:current bash Current UID/GID: 1000/1000 vyos_bld@9b72577c79da:/vyos$ vyos_bld@9b72577c79da:/vyos$ mkdir tmp && cd tmp vyos_bld@9b72577c79da:/vyos/tmp$ vyos_bld@9b72577c79da:/vyos/tmp$ git clone --recurse-submodules https://github.com/vyos/vyos-1x vyos_bld@9b72577c79da:/vyos/tmp$ vyos_bld@9b72577c79da:/vyos/tmp$ cd vyos-1x/ vyos_bld@9b72577c79da:/vyos/tmp/vyos-1x$ vyos_bld@9b72577c79da:/vyos/tmp/vyos-1x$ dpkg-buildpackage -uc -us -tc -b dpkg-buildpackage: info: source package vyos-1x dpkg-buildpackage: info: source version 1.5dev0 ...
it has been fixed about month or two ago, but still there is a problem with updated links and/or certificates.
This is still a problem. Is anyone looking into this?
Forgot to circle back on this. But it does work.
Jun 30 2025
Commands also affected: