Loading...

XML

Word

Printable

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

Hide

None

Show
None
Release Note Text:

Hide
Previously, the MicroShift clean-up script failed if CRI-O services were not present or not running. This prevented MicroShift and its dependencies from fully uninstalling. It also prevented the running of the clean-up script on a system with a new install of the `microshift-rpm` that had not started. With this release, the MicroShift clean-up script skips the CRI-O steps if the service is not running, reports that status, and continues with clean-up activities.

Show
Previously, the MicroShift clean-up script failed if CRI-O services were not present or not running. This prevented MicroShift and its dependencies from fully uninstalling. It also prevented the running of the clean-up script on a system with a new install of the `microshift-rpm` that had not started. With this release, the MicroShift clean-up script skips the CRI-O steps if the service is not running, reports that status, and continues with clean-up activities.
Release Note Type:
Bug Fix
Target Version:

4.15.0

Description of problem:

Running microshift-data-cleanup fails if crio is not running, because the crio socket is missing.

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

4.14, 4.15

How reproducible:

Steps to Reproduce:

1. Stop MicroShift
2. Stop Crio
3. Run the cleanup script

Actual results:

An error saying that crictl cannot communicate with crio because /var/run/crio/crio.sock does not exist.

Expected results:

The cleanup tool safely ignores that condition.

Additional info:

I found this issue while working on an automated test on an RPM-based host.

links to

RHEA-2023:7200 Red Hat build of MicroShift 4.15.z bug fix and enhancement update