-
Bug
-
Resolution: Done-Errata
-
Undefined
-
CNV v4.14.5
-
None
-
Incidents & Support
-
0.42
-
False
-
-
False
-
CNV v4.99.0.rhel9-533
-
-
Low
-
No
Description of problem:
If we create a PVC with 500 Gi size that ends with "000" and attach to Virtual Machine, it is getting converted to "k". This will reflect incorrect value in console.
Version-Release number of selected component (if applicable):
openshift-cnv kubevirt-hyperconverged-operator.v4.14.5
How reproducible:
Always
Steps to Reproduce:
1. Create a Disk/PVC with size that ends with "000" for example 500 Gib. # cat /tmp/pvc.yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: test-pvc namespace: nijin-cnv spec: accessModes: - ReadWriteMany resources: requests: storage: 536870912000 storageClassName: ocs-external-storagecluster-ceph-rbd volumeMode: Block # oc create -f /tmp/pvc.yaml persistentvolumeclaim/test-pvc created # oc get pvc test-pvc -o yaml |yq '.spec' accessModes: - ReadWriteMany resources: requests: storage: 536870912k <==== storageClassName: ocs-external-storagecluster-ceph-rbd volumeMode: Block volumeName: pvc-84915b3f-5366-41ee-a6dc-bfc82f6336e1 2. If we add this PVC to the VM disk, the console is showing 512.00 KiB size.
Actual results:
The console is showing incorrect size as 512.00 KiB for 500 GB PVC.
Expected results:
kubevirt plugin is taking only 536870912 bytes and not 536870912000 and hence not considering the 'k' while converting the unit. It should show correct disk size.
Additional info:
- links to
-
RHEA-2024:133097 OpenShift Virtualization 4.17.0 Images
- mentioned on