Resolved with latest changes for 6.0.0

Reportedly this problem did not exist in VyOS 1.5-rolling-202410260007 (according to slack with @evgmol ). I've seen the problem occur in versions as far back as Vyos-1.5-rolling-202411070006, so that may shed some light on where it occurs.

The individual tests look good - must be a permutation

Probably related:

It looks like this commit wasnt properly tested before pushed to the public tree according to:

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

This turns out to be a simple fix. The problem is an issue with deleting directories on separate threads when running with multiple targets. Simple fix is to run_once: true the two places where this happens. Not surprisingly, this fix works.

@HollyGurza the vyos-network-event logger service could be used to superseede netplugd which we wanted to remove for a long time.

this issue doesn't reproduce on:

found the bug in ospf_interfaces bug. This code (both for 1.3- and 1.4+) does not cut it:

likely fix PR: https://github.com/vyos/vyos-build/pull/901

Hi, I'd like to get back on this task and give it a shot, but I have troubles building and testing images from scratch.
What's the recommended procedure? Installing the latest rolling release and hacking that one?

Thank you for the feature; I really appreciate it.

The problem still exists. I tried to redirect ipv6 multicast to nflog group via nft. After that, I see multicast traffic but it is encapsulated in gre ip, not in gre ipv6. Maybe this is the issue.

I would rather fail the commit if the user tries to enable surricata and those offload types at the same time.

It will require a migration script, but otherwise it's simple to implement a check.

I suppose we could just add a "guesstimate" check, say, 2GB of free space. At the moment, rolling release images are about 600M, 2GB should be enough for a while, hopefully.

The official recommendation will be to build new images. A blog post on the flavor system is coming, and it will be in the docs, too.