Bug 2213914 - No stream for cri-o 1.26 and 1.27
Summary: No stream for cri-o 1.26 and 1.27
Keywords:
Status: CLOSED COMPLETED
Alias: None
Product: Fedora Modules
Classification: Fedora
Component: cri-o
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Douglas Schilling Landgraf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-09 21:30 UTC by Matyáš Kroupa
Modified: 2023-08-03 19:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-03 19:07:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matyáš Kroupa 2023-06-09 21:30:26 UTC
Description of problem:
Newer versions of cri-o are not available as module stream. When looking at koji, I can see that the packages were successfully built. But no updates were pushed to Bodhi.

Version-Release number of selected component (if applicable):
1.26 and 1.27

How reproducible:
On Fedora 37 and 38

Steps to Reproduce:
1. Run `dnf module list cri-o --refresh`

Actual results:
Fedora Modular 38 - x86_64
Name          Stream        Profiles           Summary                                                               
cri-o         1.22          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.23          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.24          default            Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.25          default            Kubernetes Container Runtime Interface for OCI-based containers       

Fedora Modular 38 - x86_64 - Updates
Name          Stream        Profiles           Summary                                                               
cri-o         1.22          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.23          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.24          default            Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.25          default            Kubernetes Container Runtime Interface for OCI-based containers

Expected results:
Fedora Modular 38 - x86_64
Name          Stream        Profiles           Summary                                                               
cri-o         1.22          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.23          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.24          default            Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.25          default            Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.26          default            Kubernetes Container Runtime Interface for OCI-based containers       

Fedora Modular 38 - x86_64 - Updates
Name          Stream        Profiles           Summary                                                               
cri-o         1.22          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.23          default [d]        Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.24          default            Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.25          default            Kubernetes Container Runtime Interface for OCI-based containers
cri-o         1.26          default            Kubernetes Container Runtime Interface for OCI-based containers       
cri-o         1.27          default            Kubernetes Container Runtime Interface for OCI-based containers       

Additional info:

Comment 1 Matyáš Kroupa 2023-08-03 19:07:46 UTC
The streams are now present.


Note You need to log in before you can comment on or make changes to this bug.