Vyos-build testtpm failing

It’s me again :waving_hand:

My builds are rolling again, but my smoke tests are unfortunately not. testtpm was causing me troubles already a few weeks ago. I didn’t bother too much, as we don’t have TPMs in place on our VyOS VMs, but now I’d like to tackle this and solve it for good. I’ve attached the full log of the test run to the post, but tl;dr: it complains about there being no working init, panicking the kernel at under 1 second of runtime. As these tests already had some issues due to missing/incomplete kvm flags, my suspicion is something about that being off again. Unfortunately it’s been a while since I did a deeper dive in this section, so I’d rather ask here for at least some initial pointers and maybe some help.

Best regards!

testtpm.log (281,6 KB)

I don’t even get this far:

P: Build completed successfully
Traceback (most recent call last):
  File "/vyos/./build-vyos-image", line 810, in <module>
    build()
  File "/vyos/./build-vyos-image", line 743, in build
    with subprocess.Popen(c, stdout=subprocess.PIPE, stderr=subprocess.STDOUT,
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/subprocess.py", line 1024, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.11/subprocess.py", line 1901, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'syft'
/data/vyos

Ah, you also seem to have missed the transition from “current” to “rolling” for docker tags and git branches. Just fix those references and you should get the actual current (working) releases :sweat_smile:

Not sure the communication of this change wasn’t that obvious, or it just slipped. I check the blog fairly recently (~once a month, last time ~3 weeks ago).

Ah, so I need to do more than just switch branches. Thanks, I’ll have a look.

Exactly, if you are using the docker build environment, simply switch to the vyos-build:rolling image. If you have setup the toolchain locally, you should be fine by just installing syft.

Yeah, found it, changed it, and it is building again now. Thanks again.

Were you able to replicate the test failure?

I haven’t run any tests, I’m up to my eyeballs into my project to replace 21 Sophos UTM firewalls before their license expires at the end of the month (including our datacentre cluster).

Doh :see_no_evil_monkey: fingers crossed for getting that done!

Getting slightly nervous. I’ve done one of the remotes (and the others are the same, so I don’t expect much issues there, apart from time). But the datacentre is a different kettle of fish, for starters I have no clue yet how I’m going to convert my setup to a HA cluster.

I still curse Sophos for pulling an excellent product, and offer a replacement that sucks and doesn’t cover all functionality (which blocks migration to that product). It’s been a long time since they made something, all they do is aquire, and make a botch job of it…