Loading...

XML

Word

Printable

Regression:
No
Story Points:
2
Sprint:
uShift Sprint 256
sprint_count:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
Previously, the CRI-O version was not updated in the MicroShift RPM spec file. Therefore it was possible for MicroShift to install an unsupported CRI-O in version that did not match the Kubernetes version. Now, the required version of CRI-O is updated in the MicroShift RPM spec file and the MicroShift RPM depends on correct version of CRI-O.

Show
Previously, the CRI-O version was not updated in the MicroShift RPM spec file. Therefore it was possible for MicroShift to install an unsupported CRI-O in version that did not match the Kubernetes version. Now, the required version of CRI-O is updated in the MicroShift RPM spec file and the MicroShift RPM depends on correct version of CRI-O.
Release Note Type:
Bug Fix
Release Note Status:
In Progress
Target Version:

4.14.z

Description of problem:

microshift's RPM does not specify exact minor version of crio which can lead to installing and using wrong crio and unexpected, late bugs

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

How reproducible:

Steps to Reproduce:

1.
2.
3.

Actual results:

Expected results:

Additional info:

clones

OCPBUGS-36423 [release-4.15] MicroShift RPM does not specify exact minor version of CRI-O

depends on

OCPBUGS-36423 [release-4.15] MicroShift RPM does not specify exact minor version of CRI-O

links to

RHBA-2024:4331 Red Hat build of MicroShift 4.14.z bug fix and enhancement update