crio error : "Version string empty"

[harche]

Description
Trying to install cri-o on fedora 31 by following the README.

sudo dnf module enable cri-o:1.18
sudo dnf install cri-o

But the crio won't start

Steps to reproduce the issue:

1. Follow the README for Fedora

Describe the results you received:

# crio
INFO[2020-04-28 05:54:53.084468656Z] Using conmon executable: /usr/libexec/crio/conmon 
INFO[2020-04-28 05:54:53.084746225Z] No seccomp profile specified, using the internal default 
INFO[2020-04-28 05:54:53.084764057Z] AppArmor is disabled by the system or at CRI-O build-time 
INFO[2020-04-28 05:54:53.290349433Z] Found CNI network crio (type=bridge) at /etc/cni/net.d/100-crio-bridge.conf 
INFO[2020-04-28 05:54:53.417964863Z] Found CNI network 200-loopback.conf (type=loopback) at /etc/cni/net.d/200-loopback.conf 
INFO[2020-04-28 05:54:53.998037093Z] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist 
INFO[2020-04-28 05:54:53.998074497Z] Update default CNI network name to crio      
WARN[2020-04-28 05:54:54.217153336Z] Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled 
FATA[2020-04-28 05:54:54.474225624Z] Version string empty    

# crio version 
Version:       
GitCommit:     
GitTreeState:  
BuildDate:     
GoVersion:     go1.13.9
Compiler:      gc
Platform:      linux/amd64
Linkmode:      unknown: `ldd crio` failed: ldd: ./crio: No such file or directory
  (exit status 1)

Describe the results you expected:
crio to get installed and run

Additional information you deem important (e.g. issue happens only occasionally):

Output of crio --version:

# crio version 
Version:       
GitCommit:     
GitTreeState:  
BuildDate:     
GoVersion:     go1.13.9
Compiler:      gc
Platform:      linux/amd64
Linkmode:      unknown: `ldd crio` failed: ldd: ./crio: No such file or directory
  (exit status 1)

Additional environment details (AWS, VirtualBox, physical, etc.):

[harche]

$ cat /etc/*release*
Fedora release 31 (Thirty One)
NAME=Fedora
VERSION="31 (Cloud Edition)"
ID=fedora
VERSION_ID=31
VERSION_CODENAME=""
PLATFORM_ID="platform:f31"
PRETTY_NAME="Fedora 31 (Cloud Edition)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:31"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f31/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=31
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=31
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Cloud Edition"
VARIANT_ID=cloud
Fedora release 31 (Thirty One)
Fedora release 31 (Thirty One)
cpe:/o:fedoraproject:fedora:31

[harche]

works well with crio 1.17

[haircommander]

@dougsland have we gotten v1.18.0 into OBS? it should be fixed there

[dougsland]

@haircommander for Fedora builds, we don't use OBS. We use fedora build process.

I have just sent an update to bodhi with the patch we talked this morning, should be available for testing via updates-testing soon.

Example:
# dnf module enable cri-o:1.18
# dnf install cri-o --enablerepo=updates-testing-modular

@harche thanks for the report. As soon the new package is available for updates-testing, please provide us a feedback. You can follow the state of the package here:
https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-07c39c5893

Please consider closing this report if this build works for you.

[eyanulis]

Not the original reporter - however, I encountered this problem, and installing 2:1.18.0-2.module_f32+8778+fdcfac52 from updates-testing-modular resulted in a cri-o service that can successfully start. I think this corresponds to the above mentioned build but am not quite sure how to match one to the other.

In any case I believe this is resolved by the new build. Thanks!