-
Bug
-
Resolution: Unresolved
-
Normal
-
4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.0, 4.16.z
-
Moderate
-
None
-
1
-
OCPEDGE Sprint 259
-
1
-
False
-
-
Previously it was not possible to create an LVMCluster with above 90% Size of a disk allocated for the pool. Now this is allowed, albeit with some warnings that inform users of the dangers that come along with it
-
Bug Fix
-
In Progress
This is an LVMS Bug Report:
Please make sure that you describe your storage configuration in detail. List all devices that you plan to work with for LVMS as well as any relevant machine configuration data to make it easier for an engineer to help out.
Description of problem:
https://github.com/openshift/lvm-operator/blob/b436027b9f40536b4c0cf6533c04e5690c35b8cf/api/v1alpha1/lvmcluster_types.go#L47 contains only a limitation to 90% of disk usage for the thin pool but it should be possible (with warnings) to go higher than this
Version-Release number of selected component (if applicable):
4.17.0 and below
Steps to Reproduce:
1. Create LVMCluster with thinPoolConfig, but adjust the sizePercent spec field to a value above 90, like 100 or 95
Actual results:
spec.storage.deviceClasses[0].thinPoolConfig.sizePercent in body should be less than or equal to 90" for field "spec.storage.deviceClasses[0].thinPoolConfig.sizePercent
Expected results:
Success
Additional info:
- is cloned by
-
OCPBUGS-39515 [release-4.17] LVMS thin pool used size percent configuration should allow values over 90%
- Closed
- is depended on by
-
OCPBUGS-39515 [release-4.17] LVMS thin pool used size percent configuration should allow values over 90%
- Closed
- links to
- mentioned on