Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-27177

[release-4.15] Wrong disk size filled in and cannot be changed when cloning a pvc in the UI

XMLWordPrintable

    • Important
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the *Expand PVC* modal assumed the existing PVC had a `spec.resources.requests.storage` value that includes a unit. As a result, when the *Expand PVC* modal was used to expand a PVC that had a `requests.storage` value without a unit, the console would display an incorrect value in the modal. With this update, the console was updated to handle storage values with and without a unit. (link:https://issues.redhat.com/browse/OCPBUGS-27177[*OCPBUGS-27177*])
      Show
      * Previously, the *Expand PVC* modal assumed the existing PVC had a `spec.resources.requests.storage` value that includes a unit. As a result, when the *Expand PVC* modal was used to expand a PVC that had a `requests.storage` value without a unit, the console would display an incorrect value in the modal. With this update, the console was updated to handle storage values with and without a unit. (link: https://issues.redhat.com/browse/OCPBUGS-27177 [* OCPBUGS-27177 *])
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-26772. The following is the description of the original issue:

      Description of problem:

      When cloning a PVC of 60GiB size, the system autofills the remote size to be 8192 PeB. This size cannot be changed in the UI before starting the clone.

      Version-Release number of selected component (if applicable):

      CNV - 4.14.3

      How reproducible:

      always

      Steps to Reproduce:

      1.Create a VM with a PVC of 60Gib
      2.Power off the VM
      3.As a cluster admin, clone the 60GiB PVC (Storage -> PersistentVolumeClaims -> Kebab menu next to pvc

      Actual results:

      The system tries to clone the 60 GiB PVC as a 8192 PeB

      Expected results:

      A new pvc of the 60 GiB

      Additional info:

      This seems like the closed BZ 2177979.I will upload a screenshot of the UI.
      Here is the yaml for the original pvc.
      
      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
      annotations:
      cdi.kubevirt.io/storage.bind.immediate.requested: "true"
      cdi.kubevirt.io/storage.contentType: kubevirt
      cdi.kubevirt.io/storage.pod.phase: Succeeded
      cdi.kubevirt.io/storage.populator.progress: 100.0%
      cdi.kubevirt.io/storage.preallocation.requested: "false"
      cdi.kubevirt.io/storage.usePopulator: "true"
      pv.kubernetes.io/bind-completed: "yes"
      pv.kubernetes.io/bound-by-controller: "yes"
      volume.beta.kubernetes.io/storage-provisioner: openshift-storage.rbd.csi.ceph.com
      volume.kubernetes.io/storage-provisioner: openshift-storage.rbd.csi.ceph.com
      creationTimestamp: "2023-12-05T17:34:19Z"
      finalizers:kubernetes.io/pvc-protectionprovisioner.storage.kubernetes.io/cloning-protection
      labels:
      app: containerized-data-importer
      app.kubernetes.io/component: storage
      app.kubernetes.io/managed-by: cdi-controller
      app.kubernetes.io/part-of: hyperconverged-cluster
      app.kubernetes.io/version: 4.14.0
      kubevirt.io/created-by: 60f46f91-2db3-4118-aaba-b1697b29c496
      name: win2k19-base
      namespace: base-images
      ownerReferences:apiVersion: cdi.kubevirt.io/v1beta1
      blockOwnerDeletion: true
      controller: true
      kind: DataVolume
      name: win2k19-base
      uid: 8980e7b7-ce0b-47b4-a7e4-f4c79e984ebe
      resourceVersion: "697047"
      uid: fccb0aa9-8541-4b51-b49e-ddceaa22b68c
      spec:
      accessModes:ReadWriteMany
      dataSource:
      apiGroup: cdi.kubevirt.io
      kind: VolumeImportSource
      name: volume-import-source-8980e7b7-ce0b-47b4-a7e4-f4c79e984ebe
      dataSourceRef:
      apiGroup: cdi.kubevirt.io
      kind: VolumeImportSource
      name: volume-import-source-8980e7b7-ce0b-47b4-a7e4-f4c79e984ebe
      resources:
      requests:
      storage: "64424509440"
      storageClassName: ocs-storagecluster-ceph-rbd
      volumeMode: Block
      volumeName: pvc-dbfc9fe9-5677-469d-9402-c2f3a22dab3f
      status:
      accessModes:ReadWriteMany
      capacity:
      storage: 60Gi
      phase: Bound
      
      
      
      Here is the yaml for the cloning pvc.
      
      apiVersion: v1
      kind: PersistentVolumeClaim
      metadata:
      annotations:
      volume.beta.kubernetes.io/storage-provisioner: openshift-storage.rbd.csi.ceph.com
      volume.kubernetes.io/storage-provisioner: openshift-storage.rbd.csi.ceph.com
      creationTimestamp: "2023-12-06T14:24:07Z"
      finalizers:kubernetes.io/pvc-protection
      name: win2k19-base-clone
      namespace: base-images
      resourceVersion: "1551054"
      uid: f72665c3-6408-4129-82a2-e663d8ecc0cc
      spec:
      accessModes:ReadWriteMany
      dataSource:
      apiGroup: ""
      kind: PersistentVolumeClaim
      name: win2k19-base
      dataSourceRef:
      apiGroup: ""
      kind: PersistentVolumeClaim
      name: win2k19-base
      resources:
      requests:
      storage: "9223372036854775807"
      storageClassName: ocs-storagecluster-ceph-rbd
      volumeMode: Block
      status:
      phase: Pending
      
      
      

            rhn-engineering-rhamilto Robb Hamilton
            openshift-crt-jira-prow OpenShift Prow Bot
            YaDan Pei YaDan Pei
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: