Description of problem: cri-o 1.14.9-1.module_f30+5132+c35a5687 does not start when enabled. Version-Release number of selected component (if applicable): 1.14.9-1.module_f30+5132+c35a5687 How reproducible: Install cri-o and attempt to run it via systemd. Steps to Reproduce: 1. dnf module enable -y cri-o:1.14 2. dnf install -y cri-o 3. systemctl enable --now cri-o Actual results: cri-o immediately exits, returning 1. It includes the following: time="<TIMESTAMP>" level=fatal msg="Invalid character(s) found in prerelease "module_f30"" Expected results: cri-o should start running Additional info: The error language is found in the semver parser (see, e.g., https://github.com/cri-o/cri-o/blob/master/vendor/github.com/blang/semver/semver.go). It appears that part of the cri-o build - at least on Fedora 30 builds - is the inclusion of "fedora_30" as part of the version. This string is not compatible with semantic versioning and needs to be removed from consideration by the semver code. Replacing "_" with "-" might work immediately; however, it will likely cause versioning issues later on, given the semantic(!) nature of semvers. See https://semver.org/ for a complete grammar.
Sorry, not "fedora_30", but rather "module_f30".
Is there any progress on this?
(In reply to David Haines from comment #1) > Sorry, not "fedora_30", but rather "module_f30". I can confirm the same behaviour. I was trying to use cri-o in combination with kubeadm, but did not even get beyond the start of the cri-o service. Hopefully cri-o 1.14 will work with kubeadm 1.15. According to https://github.com/cri-o/cri-o/blob/master/README.md it looks like these projects follow the same semantic versioning, but fedora 30 only includes modules up to the 1.14 version branch.
Potential duplicate of bug 1754170.
FEDORA-MODULAR-2019-749fd1db1f has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-749fd1db1f
FEDORA-MODULAR-2019-e3c905831f has been submitted as an update to Fedora 31 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-e3c905831f
cri-o-1.16-3020191115203826.a5b0195c has been pushed to the Fedora 30 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-749fd1db1f
cri-o-1.16-3120191115203826.f636be4b has been pushed to the Fedora 31 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-e3c905831f
Upgrading from cri-o-1.16.0-0.1.rc1.git6a4b481.module_f31+6837+7e34758d.x86_64 to ccri-o-1.16.0-0.4.rc2.module_f31+7054+4022d60f.x86_64 does not fix the problem: Nov 25 03:39:32 machine.example.test systemd[1]: Starting Container Runtime Interface for OCI (CRI-O)... Nov 25 03:39:32 machine.example.test crio[10053]: time="2019-11-25 03:39:32.135457557-05:00" level=fatal msg="Invalid character(s) found in build meta data \"7054+4022d60f-rc2\"" Nov 25 03:39:32 machine.example.test systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE Nov 25 03:39:32 machine.example.test systemd[1]: crio.service: Failed with result 'exit-code'. Nov 25 03:39:32 machine.example.test systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).
The original bug was on F30, now it seems like it is on F31? Which is it? If 31 we need to boot with cgroup v1 to make Kubernetes work, for now.
The issue is both on Fedora 30 (with 1.14) and on Fedora 31 (with 1.16).
FEDORA-MODULAR-2019-a955aebdcf has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-a955aebdcf
FEDORA-MODULAR-2019-24636b4ff9 has been submitted as an update to Fedora 31 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-24636b4ff9
cri-o-1.16-3020191204144621.a5b0195c has been pushed to the Fedora 30 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-a955aebdcf
cri-o-1.16-3120191204144621.f636be4b has been pushed to the Fedora 31 Modular stable repository. If problems still persist, please make note of it in this bug report.
FEDORA-MODULAR-2020-c230523214 has been submitted as an update to Fedora 30 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-c230523214
FEDORA-MODULAR-2020-36f52d4e8f has been submitted as an update to Fedora 31 Modular. https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-36f52d4e8f
cri-o-1.14-3020200226174119.a5b0195c has been pushed to the Fedora 30 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-c230523214
cri-o-1.14-3120200226174119.f636be4b has been pushed to the Fedora 31 Modular testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2020-36f52d4e8f
cri-o-1.14-3020200226174119.a5b0195c has been pushed to the Fedora 30 Modular stable repository. If problems still persist, please make note of it in this bug report.
cri-o-1.14-3120200226174119.f636be4b has been pushed to the Fedora 31 Modular stable repository. If problems still persist, please make note of it in this bug report.