It could be though some previous tests create such VRF and never clean it up.
Yes - check for previous errors
It could be though some previous tests create such VRF and never clean it up.
Yes - check for previous errors
Can we downgrade FRR to 9 for now and stick to it? 10.X has *tons* of known bugs, it should've never been released in the state it's in, even now at 10.2. @Viacheslav @c-po is this feasible to stick with 9.X for now until 10 stabilizes more?
Needs to check if our version is affected this bug https://github.com/FRRouting/frr/issues/18555
@L0crian cf. https://vyos.dev/T6740, which provides a converter: set commands -> config
Not enabling forwarding fixes this behaviour
Fix in this PR https://github.com/vyos/vyos-vpp/pull/25
Any chance this might be backported to 1.4 ?
Most likely, the package cannot build or CI has temporary issues to build it
Was added recently https://github.com/vyos/vyos-build/commit/282ca5b30813a19c5af5c14127ec483409dae14c
PR incoming shortly.
Pull request created to fix this issue:
https://github.com/vyos/vyos-1x/pull/4433
Note that the duplicate messages are malformed - including what looks like part of the time stamp at the beginning of the message entry.
@dmbaturin Are you sure that should be 100 instead of a two digit number? I think those will be done in lexicographic order, I suspect there may be confusion generated if someone tries to make a 110, and 11 runs first.
Thank you for the quick response to this, and the work to mitigate it 🙌
@mjones-vsat I think the wording is good.