-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.17
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
None
-
None
-
None
-
uShift Sprint 268, uShift Sprint 269, uShift Sprint 270, uShift Sprint 271, uShift Sprint 272, uShift Sprint 273, uShift Sprint 274, uShift Sprint 275, uShift Sprint 276
-
9
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When I create local LVM device class in lvmd.yaml with given name as in docs examples, the name won't apply to generated storageClass.
Version-Release number of selected component (if applicable):
microshift-4.17.14-202501240429.p0.gd53a093.assembly.4.17.14.el9.aarch64
How reproducible:
Constantly
Steps to Reproduce:
1. Create file. /etc/microshift/lvmd.yaml:
socket-name: /run/lvmd/lvmd.socket
device-classes:
- name: ssd-lvm
volume-group: ssd
spare-gb: 20
default: true
2. start microshift
3. The created SC is not ssd-lvm, but topolvm-provisioner. It works but has wrong name.
Actual results:
$ oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE topolvm-provisioner (default) topolvm.io Delete WaitForFirstConsumer true 4d13h
Expected results:
SC should have the name of device class, as how I understood it in our docs:
https://docs.redhat.com/en/documentation/red_hat_build_of_microshift/4.17/html/storage/microshift-storage-plugin-overview#microshift-storage-device-classes_microshift-storage-plugin-overview
Additional info:
Discussed in slack here: https://redhat-internal.slack.com/archives/C03DP9PABNC/p1738756695576449
- is related to
-
-
- Closed
-
