-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
CLOSED
-
-
-
Moderate
-
None
Description of problem:
This one needs a bit of specific numerology to reproduce.
I noticed it in one of my VMs by chance.
Basically:
- Pre-configured PV of 563G (I'm using LSO)
- VM disk PVC of 500G binds to the PV above
Result: the UI shows the disk as 512KiB.
If I move things around (i.e. change some of the sizes, the problem goes away).
Version-Release number of selected component (if applicable):
4.12.2
How reproducible:
Always
Steps to Reproduce:
1. Using LSO, create a 563G partition (I have some of 100 and 200G which do not reproduce)
$ sudo fdisk -l /dev/sda | grep -E 'Device|sda14 '
Device Start End Sectors Size Type
/dev/sda14 2726299648 3907029134 1180729487 563G Linux filesystem
2. Let LSO create the PV for it
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
local-pv-6079dbae 563Gi RWO Delete Available local-ssd 27m
3. Create a VM disk in such a way that it will bind to the PV above. But request only 500G
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
fedora-disk-bad-swift Bound local-pv-6079dbae 563Gi RWO local-ssd 30m
4. Navigate to the console, Virtual Machines -> VM -> Disks. See the size it reports.
See the screenshot attached for the exact case above.
Actual results:
512K
Expected results:
563G
Additional info:
- Only happens with very specific values
- external trackers
- links to
-
RHEA-2024:133097 OpenShift Virtualization 4.17.0 Images