-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.14
-
None
Description of problem:
When expanding a PVC of unit-less size (e.g., '2147483648'), the Expand PersistentVolumeClaim modal populates the spinner with a unit-less value (e.g., 2147483648) instead of a meaningful value.
Version-Release number of selected component (if applicable):
CNV - 4.14.3
How reproducible:
always
Steps to Reproduce:
1.Create a PVC using the following YAML.
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: task-pv-claim spec: storageClassName: gp3-csi accessModes: - ReadWriteOnce resources: requests: storage: "2147483648"
apiVersion: v1 kind: Pod metadata: name: task-pv-pod spec: securityContext: runAsNonRoot: true seccompProfile: type: RuntimeDefault volumes: - name: task-pv-storage persistentVolumeClaim: claimName: task-pv-claim containers: - name: task-pv-container image: nginx ports: - containerPort: 80 name: "http-server" volumeMounts: - mountPath: "/usr/share/nginx/html" name: task-pv-storage
2. From the newly created PVC details page, Click Actions > Expand PVC. 3. Note the value in the spinner input.
See https://drive.google.com/file/d/1toastX8rCBtUzx5M-83c9Xxe5iPA8fNQ/view for a demo
- blocks
-
OCPBUGS-27909 [release-4.15] Wrong disk size filled in when expanding a pvc in the UI
- Closed
- clones
-
OCPBUGS-26772 Wrong disk size filled in and cannot be changed when cloning a pvc in the UI
- Closed
- is cloned by
-
OCPBUGS-27909 [release-4.15] Wrong disk size filled in when expanding a pvc in the UI
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update