Kubernetes, CRI-O, and CRI-Tools exist in F40 and F41 as both unversioned rpms (e.g. cri-o-1.30.6) and versioned rpms (e.g cri-o1.30-1.30.6). The original transition plan for unversioned to versioned was to hold the unversioned rpms at v1.29 (all 3 packages are intended to be synchronized on major:minor versions for installation).
Unversioned CRI-O for F41 was inadvertently bumped from v1.29 to v1.30. I request that the committee approve a corresponding bump for unversioned Kubernetes and CRI-Tools to their respective v1.30 releases. Email to the developer community and a Fedora Community Blog post will announce the forthcoming change if the change request is approved. Versioned rpms are available as an alternative and will also be highlighted.
I'm not sure what FPC can do here? If you're asking for an exception to the Updates Policy, that would need to be addressed to FESCo, instead.
That said, I'm confused by what version the cri-o package is supposed to provide ... I don't see a pattern here, other than that the f41 branch ships 1.30 (redundant with cri-o1.30), the f40 branch ships something older, and the rawhide branch ships something newer ...
Should the unsuffixed cri-o package be retired? I don't think it makes sense to keep it, if you're providing versioned cri-o packages anyway (to avoid confusion and duplication).
Thanks for the guidance. I will submit a request to FESCO.
The maintainers for CRI-O, CRI-Tools, and Kubernetes had an agreement to (1) provide the same major:minor version for a given Fedora release and (2) to keep F40 and F41 at v1.29 and (3) retire in F42.
CRI-O updates to F41 and F42 were submitted (v1.30 and v1.31) by someone not aware of the agreement. Subsequently CRI-O upstream made changes that triggered FTBFS for these versions. Updates to CRI-O have been submitted that resolve the FTBFS status. We now need to bring Kubernetes and CRI-Tools into version alignment with Kubernetes as there are some Recommends that enforce the same version agreement.
Metadata Update from @buckaroogeek: - Issue close_status updated to: nothingtodo - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.