Looks like it is related to T5324

This is the bad one:
Oct 28 18:03:45 debian vyos_net_name[896]: Started with arguments: ['/lib/udev/vyos_net_name', 'e8']
Oct 28 18:03:45 debian vyos_net_name[886]: Started with arguments: ['/lib/udev/vyos_net_name', 'e4', '00:0c:29:2d:44:53', 'eth4']
Oct 28 18:03:45 debian vyos_net_name[888]: Started with arguments: ['/lib/udev/vyos_net_name', 'e6', '00:0c:29:2d:44:3f', 'eth2']
Oct 28 18:03:45 debian vyos_net_name[887]: Started with arguments: ['/lib/udev/vyos_net_name', 'e5', '00:0c:29:2d:44:35', 'eth1']
Oct 28 18:03:45 debian vyos_net_name[884]: Started with arguments: ['/lib/udev/vyos_net_name', 'e3', '00:0c:29:2d:44:49', 'eth3']
Oct 28 18:03:45 debian vyos_net_name[885]: Started with arguments: ['/lib/udev/vyos_net_name', 'e2', '00:0c:29:2d:44:2b', 'eth0']
e7 is missing e8 has no mac address

FTR --ncp-disable was only supposed to disable the cipher negotiation. It was not meant to disable encryption entirely. --data-ciphers none is the way to go, but it seems you've already figure this out.

@dmbaturin, what is the state of this?

@SteveP could you attach those files for debugging where the issue exists?

/config/config.boot
/run/udev/log/vyos-net-name 
sudo journalctl -b | tee /tmp/journalct.log
sudo journalctl -k | tee /tmp/journalct-k.log

Yes for Circinus; I think not advisable for Sagitta, but let us ask @dmbaturin for opinion.

No worries, I'm all good here. I can turn off signing and carry on with the unsigned drivers as before. It is all good if I load them in the pre-script. If I figure it out I'll let you know.

I’d prefer to drop it at all for now.
Until someone can investigate it more deeply.
I don’t have any idea what is wrong.
Thanks

Looking at dmesg from a working config we can see:

On systems that do not support SecureBoot, mokutil will exit with code 255. This causes show version to break as the cmd() that launches it raises an error. The mokutil execution through cmd() should catch that return code as normal:

nothing in the difference between .51 & .52. I'm beginning to doubt myself now that that was the point it broke. That was also the point where you started requiring signed drivers and maybe I'm conflating the problems I had at that point.

Still broken I'm afraid.

@SteveP Can you try the latest rolling?

PR list below; after the first two are reviewed/merged, the others can be moved out of draft, in order of dependencies.
https://github.com/vyos/vyconf/pull/11
https://github.com/vyos/vyos1x-config/pull/31
https://github.com/vyos/vyatta-cfg/pull/94
https://github.com/vyos/libvyosconfig/pull/21
https://github.com/vyos/vyos-build/pull/824
https://github.com/vyos/vyos-1x/pull/4176
https://github.com/vyos/vyatta-cfg/pull/95

I just built from the current top-of-tree and installed onto my working system and I no longer am getting that log message filling up my system logs. I'm not sure if something indirectly fixed it or what - regardless it appears fixed now. Therefore, I'm moving the status to resolved.

The issue of breaking smoketest is not with iproute2

Updated repos below; one minor change needed for replacements to my_set/my_delete before PR:

also save information about the temporary package version: https://github.com/vyos/vyos-build/pull/820#event-14849025089

• Team upload
  • Revert "Drop legacy /usr/sbin/ip symlink", as many packages still depend on /sbin/ip or /usr/sbin/ip

I am sorry I just found another task with same issue, https://vyos.dev/T6770, Please close this task.