Bug 1977567
| Summary: | The 'nightly' and '1.20' cri-o modules actually have 1.19 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora Modules | Reporter: | David Gibson <dgibson> |
| Component: | cri-o | Assignee: | Douglas Schilling Landgraf <dougsland> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | dougsland, fidencio, pehunt, ppisar, rh.container.bot, umohnani |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cri-o-1.20-3420211111195901.058368ca | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-08 11:51:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1970050 | ||
| Bug Blocks: | |||
Apart from the issue with the cri-o package itself, the cri-tools package seems to be messed up. In the 1.20 module it also has a 1.19 version, in the nightly module it has a 1.18 (!?) version. This won't be solved till https://bugzilla.redhat.com/show_bug.cgi?id=1970050 is solved. The oldest supported Fedora is 34 and cri-o:1.20 stream there contains cri-o-0:1.20.0-1.module_f34+10489+4277ba4d and cri-tools-0:1.20.0-2.module_f34+13352+1a243f1a.x86_64 packages. The nightly stream does not exist anymore. |
Description of problem: Version-Release number of selected component (if applicable): Fedora 34 How reproducible: 100% Steps to Reproduce: 1. Enable cri-o nightly module # dnf enable cri-o:nightly 2. Look for available cri-o version Actual results: $ dnf module list cri-o Last metadata expiration check: 0:04:02 ago on Wed 30 Jun 2021 14:15:37. Fedora Modular 34 - x86_64 Name Stream Profiles Summary cri-o nightly [e] default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.17 default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.18 default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.19 default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.20 default Kubernetes Container Runtime Interface for OCI-based containers Fedora Modular 34 - x86_64 - Updates Name Stream Profiles Summary cri-o nightly [e] default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.17 default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.18 default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.19 default Kubernetes Container Runtime Interface for OCI-based containers cri-o 1.20 default Kubernetes Container Runtime Interface for OCI-based containers Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled $ dnf info cri-o Last metadata expiration check: 0:04:09 ago on Wed 30 Jun 2021 14:15:37. Installed Packages Name : cri-o Epoch : 2 Version : 1.19.0 Release : 43.gitc00d425.module_f34+10209+fb610d12 Architecture : x86_64 Size : 105 M Source : cri-o-1.19.0-43.gitc00d425.module_f34+10209+fb610d12.src.rpm Repository : @System From repo : fedora-modular Summary : Kubernetes Container Runtime Interface for OCI-based containers URL : https://github.com/cri-o/cri-o License : ASL 2.0 Description : Kubernetes Container Runtime Interface for OCI-based containers Expected results: Shows a more recent version of CRI-O (at least 1.20, preferably 1.21). Same problem shows up with 1.20 module version, it only shows a 1.19 package version. Additional info: * This breaks my use case because the 1.19 CRI-O doesn't have this fix: https://github.com/cri-o/cri-o/issues/4589 * I see some 1.20 builds in Koji for F34. Those appear to have Epoch 0, whereas the 1.19 package has Epoch 2. Not sure if this is related.