Bug 1830159

Description of problem:
crio service will not start

Version-Release number of selected component (if applicable):
1.18

How reproducible:
always

Steps to Reproduce:
per https://cri-o.io/
1. VERSION=1.18
2. dnf module enable cri-o:$VERSION
3. dnf install cri-o
4. systemctl enable --now crio

Actual results:
# 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).

Expected results:
● 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 info:
I tried setting selinux to permissive.  systemctl restart yields same failure.