-
Bug
-
Resolution: Done-Errata
-
Major
-
4.17.0, 4.16.z
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
No
-
None
-
Rejected
-
OCPEDGE Sprint 255
-
1
-
In Progress
-
Bug Fix
-
Previously, the LVMCluster custom resource (CR) would report a *Ready* state even when no volume groups (VGs) had been created. With this fix, the `LVMCluster` CR reports *Progressing* state to indicate that the VGs are not yet ready.
-
None
-
None
-
None
-
None
Description of problem:
LVMCluster is in Ready state although there is no VGs created because of a problematic node selector:
Spec: Storage: Device Classes: Default: true Fstype: xfs Name: vg1 Node Selector: Node Selector Terms: Match Expressions: Key: kubernetes.io/hostname Operator: In Values: test Thin Pool Config: Chunk Size Calculation Policy: Static Name: thin-pool-1 Overprovision Ratio: 10 Size Percent: 90 Status: Conditions: Last Transition Time: 2024-06-19T09:08:36Z Message: Reconciliation is complete and all the resources are available Reason: ResourcesAvailable Status: True Type: ResourcesAvailable Last Transition Time: 2024-06-19T09:08:36Z Message: All the VGs are ready Reason: VGsReady Status: True Type: VolumeGroupsReady Ready: true State: Ready
