Managed nodes stuck in init on Ubuntu 20.04

[ranweiler]

Observed on OneFuzz 2.23.1.

Repro

1. Create a Linux pool: onefuzz pools create ubuntu-2004 linux
2. Create a scaleset on the pool with the latest official Ubuntu 20.04 image: onefuzz scalesets create ubuntu-2004 5 --image Canonical:0001-com-ubuntu-server-focal:20_04-lts:latest

Expected

The nodes in the scaleset enter init, then free, waiting for work.

Actual

The nodes enter init, but never advanced, even after up to 24 hours.

[ranweiler]

Quick investigation turns up the following in syslog:

onefuzz-supervisor: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory

Full start attempt:

Jun 30 00:23:04 node000000 systemd[1]: Started onefuzz.
Jun 30 00:23:04 node000000 bash[65366]: + export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/onefuzz/bin:/onefuzz/tools/linux:/onefuzz/tools/linux/afl:/onefuzz/tools/linux/radamsa
Jun 30 00:23:04 node000000 bash[65366]: + PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/onefuzz/bin:/onefuzz/tools/linux:/onefuzz/tools/linux/afl:/onefuzz/tools/linux/radamsa
Jun 30 00:23:04 node000000 bash[65366]: + export ONEFUZZ_TOOLS=/onefuzz/tools
Jun 30 00:23:04 node000000 bash[65366]: + ONEFUZZ_TOOLS=/onefuzz/tools
Jun 30 00:23:04 node000000 bash[65366]: + export ONEFUZZ_ROOT=/onefuzz
Jun 30 00:23:04 node000000 bash[65366]: + ONEFUZZ_ROOT=/onefuzz
Jun 30 00:23:04 node000000 bash[65366]: + export RUST_BACKTRACE=full
Jun 30 00:23:04 node000000 bash[65366]: + RUST_BACKTRACE=full
Jun 30 00:23:04 node000000 bash[65366]: + export RUST_LOG=info
Jun 30 00:23:04 node000000 bash[65366]: + RUST_LOG=info
Jun 30 00:23:04 node000000 bash[65366]: + export ASAN_SYMBOLIZER_PATH=/onefuzz/bin/llvm-symbolizer
Jun 30 00:23:04 node000000 bash[65366]: + ASAN_SYMBOLIZER_PATH=/onefuzz/bin/llvm-symbolizer
Jun 30 00:23:04 node000000 bash[65366]: + logger 'onefuzz: starting up onefuzz'
Jun 30 00:23:04 node000000 root: onefuzz: starting up onefuzz
Jun 30 00:23:04 node000000 bash[65369]: + sudo tee /proc/sys/kernel/core_pattern
Jun 30 00:23:04 node000000 bash[65368]: + echo core
Jun 30 00:23:04 node000000 bash[65370]: core
Jun 30 00:23:04 node000000 bash[65371]: + echo 0
Jun 30 00:23:04 node000000 bash[65372]: + sudo tee /proc/sys/kernel/randomize_va_space
Jun 30 00:23:04 node000000 bash[65373]: 0
Jun 30 00:23:04 node000000 bash[65374]: + echo 1
Jun 30 00:23:04 node000000 bash[65375]: + sudo tee /proc/sys/fs/suid_dumpable
Jun 30 00:23:04 node000000 bash[65376]: 1
Jun 30 00:23:04 node000000 bash[65366]: + cd /onefuzz
Jun 30 00:23:04 node000000 bash[65377]: ++ cat /onefuzz/etc/mode
Jun 30 00:23:04 node000000 bash[65366]: + MODE=fuzz
Jun 30 00:23:04 node000000 bash[65366]: + case ${MODE} in
Jun 30 00:23:04 node000000 bash[65366]: + logger 'onefuzz: starting fuzzing'
Jun 30 00:23:04 node000000 root: onefuzz: starting fuzzing
Jun 30 00:23:04 node000000 bash[65366]: + echo fuzzing
Jun 30 00:23:04 node000000 bash[65366]: fuzzing
Jun 30 00:23:04 node000000 bash[65366]: + onefuzz-supervisor run --config /onefuzz/config.json
Jun 30 00:23:04 node000000 bash[65379]: onefuzz-supervisor: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
Jun 30 00:23:04 node000000 systemd[1]: onefuzz.service: Main process exited, code=exited, status=127/n/a
Jun 30 00:23:04 node000000 systemd[1]: onefuzz.service: Failed with result 'exit-code'.

[ranweiler]

Reopened by #1721, via the Azure SDK for Rust dependencies (h/t @nharper285).