Loading...

XML

Word

Printable

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

Hide

None

Show
None
Release Note Text:

Hide
Previously, MicroShift did not log its version at start up. The absence of version information made debugging certain scenarios difficult because the update path was unknown. Now, the MicroShift version is logged at start up and available to commands such as `journalctl -u microshift | grep "$current-version"`.

Show
Previously, MicroShift did not log its version at start up. The absence of version information made debugging certain scenarios difficult because the update path was unknown. Now, the MicroShift version is logged at start up and available to commands such as `journalctl -u microshift | grep "$current-version"`.
Release Note Type:
Feature
Release Note Status:
In Progress
Target Version:

4.15.0

Description of problem:

MicroShift doesn't print its version so it's more difficult to debug some scenarios because of unknown upgrade path

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

How reproducible:

Steps to Reproduce:

1. journalctl -u microshift | grep "$current-version like 4.14.0"
2.
3.

Actual results:

no mention of microshift's version

Expected results:

microshift logs its version (OCP base, commit, release, etc.)

Additional info:

blocks

OCPBUGS-19638 MicroShift doesn't print its version at the start

is cloned by

OCPBUGS-19638 MicroShift doesn't print its version at the start

links to

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