Boulder integration test fail on wsl:

Unknown subcommand "admin".
Traceback (most recent call last):
  File "test/", line 149, in <module>
  File "test/", line 93, in main
  File "test/", line 116, in run_chisel
  File "/boulder/test/", line 1609, in test_admin_revoker_batched
  File "/boulder/test/", line 53, in run
    return subprocess.check_call(cmd, stderr=subprocess.STDOUT, **kwargs)
  File "/usr/lib/python3.8/", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['./bin/admin', '-config', 'test/config/admin.json', '-dry-run=false', 'revoke-cert', '-serials-file', '/tmp/tmplajcv7si/tmpdoqnax4t.test_admin_revoker_batched.serials.hex', '-reason', 'unspecified', '-parallelism', '2']' returned non-zero exit status 1.
08:37:18.858958 6 akamai-purger 2f7Ciwo Shutting down; queue is already empty.
FAILURE while running integration

this only happens when it's run on wsl, not on native, but it fails on anything on docker over wsl: (both docker desktop on window calling wsl and docker directly installed on wsl ubuntu: may better asked on wsl forum but error itself is on boulder side errror that admin is not registerd while compiling, so it'd known better on here


The admin command has moved from a subcommand in the Boulder binary to a standalone binary.

I think there’s some cases where it’s not rebuilt properly. Look if there’s an admin symlink in the bin/ folder, delete it, and try running again


that was it, thanks!


Also symlinks between WSL and windows are unpredictable and often don't work well if the affected part of your filesystem spans Windows > Linux or back again, in particular they don't work on ReFS volumes (for me).

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.