-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.11.z
-
None
-
Moderate
-
False
-
Description of problem:
TopoLVM is using a PV (created by LSO) while its status is "Available". TopoLVM's Storage Capacity doesn't match the PV size.
Version-Release number of selected component (if applicable):
*odf-lvm-operator.v4.11.3*
How reproducible:
Steps to Reproduce:
1. SNO Bare metal - deploy OCP 4.12
2. Deploy LSO - it created a PV of 446 Gi
3. Deploy TopoLVM - odf-lvm-operator.v4.11.3
apiVersion: lvm.topolvm.io/v1alpha1 kind: LVMCluster metadata: finalizers: - lvmcluster.topolvm.io name: odf-lvmcluster namespace: openshift-storage spec: storage: deviceClasses: - name: vg1 thinPoolConfig: name: thin-pool-1 overprovisionRatio: 10 sizePercent: 90
Actual results:
$ oc get pv local-pv-74b43d87 -o yaml | grep -e Available -e sdb
storage.openshift.com/device-name: sdb
phase: Available
TopoLVM is using the LSO PV while PV is shown "Available"
[core@cnv-qe-infra-24 ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 1G 0 loop
sda 8:0 0 558.4G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 127M 0 part
├─sda3 8:3 0 384M 0 part /boot
└─sda4 8:4 0 557.9G 0 part /sysroot
sdb 8:16 0 446.6G 0 disk
├─vg1-thin--pool--1_tmeta 253:0 0 52M 0 lvm
│ └─vg1-thin--pool--1-tpool 253:2 0 401.9G 0 lvm
│ ├─vg1-thin--pool--1 253:3 0 401.9G 1 lvm
│ ├─vg1-e657234e--2317--4733--9ecf--7d420d91478c 253:4 0 1G 0 lvm
│ ├─vg1-cad5e45e--b904--4052--ba8c--bf3fa7a365b3 253:5 0 30G 0 lvm
│ ├─vg1-ecd4c764--fcd6--4539--b2a2--592c4aa6e036 253:6 0 30G 0 lvm
│ ├─vg1-b87911a2--09a0--44c5--be5f--ba262a1874ac 253:7 0 30G 0 lvm
│ ├─vg1-b4c3e700--dd41--4a14--8d44--6b62d9bdbed2 253:8 0 30G 0 lvm
│ ├─vg1-64ed3ffa--65dc--4db6--a856--d53e2e8fa364 253:9 0 30G 0 lvm
│ └─vg1-1c8f10fc--7387--402d--8c8a--baf0fd45e186 253:10 0 30G 0 lvm
└─vg1-thin--pool--1_tdata 253:1 0 401.9G 0 lvm
└─vg1-thin--pool--1-tpool 253:2 0 401.9G 0 lvm
├─vg1-thin--pool--1 253:3 0 401.9G 1 lvm
├─vg1-e657234e--2317--4733--9ecf--7d420d91478c 253:4 0 1G 0 lvm
├─vg1-cad5e45e--b904--4052--ba8c--bf3fa7a365b3 253:5 0 30G 0 lvm
├─vg1-ecd4c764--fcd6--4539--b2a2--592c4aa6e036 253:6 0 30G 0 lvm
├─vg1-b87911a2--09a0--44c5--be5f--ba262a1874ac 253:7 0 30G 0 lvm
├─vg1-b4c3e700--dd41--4a14--8d44--6b62d9bdbed2 253:8 0 30G 0 lvm
├─vg1-64ed3ffa--65dc--4db6--a856--d53e2e8fa364 253:9 0 30G 0 lvm
└─vg1-1c8f10fc--7387--402d--8c8a--baf0fd45e186 253:10 0 30G 0 lvm
TopoLVM's Storage Capacity doesn't match the PV size
$ oc get csiStorageCapacity -n openshift-storage csisc-78wcw -oyaml | grep capacity capacity: 3929656Mi
3929656 Mi / 1024 = 3837 Gi (while LSO PV is 446 Gi)
Expected results:
If TopoLVM is using a PV, PV shouldn't be marked as "Available". csiStorageCapacity should show me the real storage capacity.
Additional info:
I may get you a live cluster for debugging.