I have a fresh install of Fedora 32 and cri-o 1.18. crio fails to start at systemctl enable --now crio

Steps to reproduce the issue:

1. Install Fedora 32
2. Install crio per https://cri-o.io/
3. systemctl enable --now crio

Describe the results you received:

systemctl status crio --no-pager -l

● crio.service - Container Runtime Interface for OCI (CRI-O) Loaded: loaded (/usr/lib/systemd/system/crio.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Thu 2020-04-30 16:31:17 PDT; 12min ago Docs: https://github.com/cri-o/cri-o Process: 922 ExecStart=/usr/bin/crio $CRIO_CONFIG_OPTIONS $CRIO_RUNTIME_OPTIONS $CRIO_STORAGE_OPTIONS $CRIO_NETWORK_OPTIONS $CRIO_METRICS_OPTIONS (code=exited, status=1/FAILURE) Main PID: 922 (code=exited, status=1/FAILURE) CPU: 208ms

Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.508525817-07:00” level=info msg=“AppArmor is disabled by the system or at CRI-O build-time” Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.522845028-07:00” level=info msg=“Found CNI network crio (type=bridge) at /etc/cni/net.d/100-crio-bridge.conf” Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.533307816-07:00” level=info msg=“Found CNI network 200-loopback.conf (type=loopback) at /etc/cni/net.d/200-loopback.conf” Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.576317230-07:00” level=info msg=“Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist” Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.576341624-07:00” level=info msg=“Update default CNI network name to crio” Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.793353021-07:00” level=warning msg=“Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled” Apr 30 16:31:17 cube0 crio[922]: time=“2020-04-30 16:31:17.796965936-07:00” level=fatal msg=“Version string empty” Apr 30 16:31:17 cube0 systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE Apr 30 16:31:17 cube0 systemd[1]: crio.service: Failed with result ‘exit-code’. Apr 30 16:31:17 cube0 systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).

Describe the results you expected: ● crio.service - Container Runtime Interface for OCI (CRI-O) Loaded: loaded (/usr/lib/systemd/system/crio.service; enabled; vendor preset: disabled) Active: active (running) since fooor evvv aaaah

Additional information you deem important (e.g. issue happens only occasionally): I tried setting selinux to permissive. systemctl restart yields same failure.

Output of crio --version:

[root@cube0 ~]# crio --version
crio version
Version:
GitCommit:
GitTreeState:
BuildDate:
GoVersion:     go1.14
Compiler:      gc
Platform:      linux/amd64
Linkmode:      unknown: `ldd crio` failed: ldd: ./crio: No such file or directory
  (exit status 1)
[root@cube0 ~]# which crio
/usr/bin/crio
[root@cube0 ~]# ldd /usr/bin/crio
	linux-vdso.so.1 (0x00007fffbc79d000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1149e9c000)
	libseccomp.so.2 => /lib64/libseccomp.so.2 (0x00007f1149e4e000)
	libgpgme.so.11 => /lib64/libgpgme.so.11 (0x00007f1149dfc000)
	libassuan.so.0 => /lib64/libassuan.so.0 (0x00007f1149de6000)
	libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007f1149dc2000)
	libdevmapper.so.1.02 => /lib64/libdevmapper.so.1.02 (0x00007f1149d64000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f1149d57000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f1149b8d000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f114d9f6000)
	libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f1149b60000)
	libudev.so.1 => /lib64/libudev.so.1 (0x00007f1149b36000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f11499f0000)
	libpcre2-8.so.0 => /lib64/libpcre2-8.so.0 (0x00007f1149957000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f114994e000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f1149933000)

Additional environment details (AWS, VirtualBox, physical, etc.): physical … HP EliteDesk Mini G2 (Intel Core i5 / 16 gig mem)

Bugzilla is here