-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.14.z
-
Important
-
None
-
False
-
-
Description of problem:
The customer added a 4T disk to the node and used Local Volume cr to create the disk to create StorageClass. The customer found that the capacity displayed by pv was 1T.
(if applicable):
local-storage-operator.v4.14.0-202403261739
How reproducible:
Steps to Reproduce:
1.apiVersion: local.storage.openshift.io/v1 kind: LocalVolume metadata: annotations: kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"local.storage.openshift.io/v1","kind":"LocalVolume","metadata":{"annotations":{},"name":"odf-03-disk-03","namespace":"openshift-local-storage"},"spec":{"nodeSelector":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"kubernetes.io/hostname","operator":"In","values":["odf-03.pnr.nia.gov.tw"]}]}]},"storageClassDevices":[{"devicePaths":["/dev/disk/by-id/wwn-0x6000c294bdefe1b688f5f6e4279f637c"],"storageClassName":"odf-local-volume-tmp","volumeMode":"Block"}]}} creationTimestamp: "2024-12-06T10:40:00Z" finalizers: - storage.openshift.com/local-volume-protection generation: 2 name: odf-03-disk-03 namespace: openshift-local-storage resourceVersion: "267413217" uid: 6b8c571a-aedf-4fb7-bae8-6eeb6f6e4f7a spec: logLevel: Normal managementState: Managed nodeSelector: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - odf-03.pnr.nia.gov.tw storageClassDevices: - devicePaths: - /dev/disk/by-id/wwn-0x6000c294bdefe1b688f5f6e4279f637c storageClassName: odf-local-volume-tmp volumeMode: Block status: conditions: - lastTransitionTime: "2024-12-06T10:40:00Z" message: Ready status: "True" type: Available generations: - group: apps lastGeneration: 11 name: diskmaker-manager namespace: openshift-local-storage resource: DaemonSet managementState: Managed observedGeneration: 2 readyReplicas: 0 2. omc get pvc|grep odf-local-volume-tmp ocs-deviceset-odf-local-volume-tmp-0-data-0cqrfv Bound local-pv-1fb74fa6 4Ti RWO odf-local-volume-tmp 1d ocs-deviceset-odf-local-volume-tmp-0-data-18kth5 Bound local-pv-7cff1804 1Ti RWO odf-local-volume-tmp 1d ocs-deviceset-odf-local-volume-tmp-0-data-26zd2g Bound local-pv-91df864f 1Ti RWO odf-local-volume-tmp 1d omc get pv |grep odf-local-volume-tmp local-pv-1fb74fa6 4Ti RWO Delete Bound openshift-storage/ocs-deviceset-odf-local-volume-tmp-0-data-0cqrfv odf-local-volume-tmp 6d local-pv-7cff1804 1Ti RWO Delete Bound openshift-storage/ocs-deviceset-odf-local-volume-tmp-0-data-18kth5 odf-local-volume-tmp 6d local-pv-91df864f 1Ti RWO Delete Bound openshift-storage/ocs-deviceset-odf-local-volume-tmp-0-data-26zd2g odf-local-volume-tmp 6d 3.
Actual results:
One pv is displayed as 4T, two pvs are displayed as 1T
Expected results:
The three pvs should be displayed as 4T.
Additional info:
sosreport link : https://attachments.access.redhat.com/hydra/rest/cases/04011983/attachments/105ee852-9592-42b2-a798-237f6b2a8adf?usePresignedUrl=true project dump link : https://attachments.access.redhat.com/hydra/rest/cases/04011983/attachments/373973bd-93c0-4621-9e45-c4ad904bd637?usePresignedUrl=true