-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.14.z
-
No
-
2
-
uShift Sprint 246, uShift Sprint 247, uShift Sprint 248
-
3
-
False
-
-
-
Bug Fix
-
In Progress
This is a clone of issue OCPBUGS-24444. The following is the description of the original issue:
—
Description of problem:
The docs say "The default integration of LVMS selects the default volume group (VG) dynamically. If there are no volume groups on the MicroShift host, LVMS is disabled." When LVMS is disabled, we need to skip greenboot check for `openshift-storage` namespace
Version-Release number of selected component (if applicable):
4.14
How reproducible:
100%
Steps to Reproduce:
1. Boot microshift would LVM volume groups
Actual results:
Greenboot reports RED
Expected results:
Greenboot should report GREEN
- clones
-
OCPBUGS-24444 MicroShift greenboot reports RED when no volume groups exist
- Closed
- is blocked by
-
OCPBUGS-24444 MicroShift greenboot reports RED when no volume groups exist
- Closed
- links to
-
RHEA-2023:7200 Red Hat build of MicroShift 4.15 bug fix and enhancement update