Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-23311

[2152537] [4.13]Better to have a more friendly error when missing storage size in clone

XMLWordPrintable

    • Storage Core Sprint 229, Storage Core Sprint 230, Storage Core Sprint 231
    • High
    • None

      Description of problem:
      Better to have a more friendly error when missing storage size in clone

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

      How reproducible:
      Always

      Steps to Reproduce:
      1. Clone from a pvc without setting storage size in DataVolume.spec.storage.resources


      apiVersion: cdi.kubevirt.io/v1beta1
      kind: DataVolume
      metadata:
      name: clone4
      annotations:
      cdi.kubevirt.io/cloneType: ""
      cdi.kubevirt.io/storage.bind.immediate.requested: "true"
      cdi.kubevirt.io/storage.deleteAfterCompletion: "false"
      spec:
      source:
      pvc:
      name: fedora-56ccabc01cbe
      namespace: openshift-virtualization-os-images
      storage:
      resources: {}

      Actual results:
      1. The DV keeps in CloneScheduled status, no progress
      2. Describe the dv, only got warning "The size detection pod is not finished yet"
      Events:
      Type Reason Age From Message
      ---- ------ ---- ---- -------
      Normal SizeDetectionPodCreated 4m44s datavolume-controller Size-detection pod created
      Normal CloneScheduled 4m44s datavolume-controller Cloning from openshift-virtualization-os-images/fedora-56ccabc01cbe into default/clone4 scheduled
      Normal CloneScheduled 4m44s datavolume-controller No PVC found
      Normal SizeDetectionPodNotReady 4m42s (x11 over 4m44s) datavolume-controller The size detection pod is not finished yet
      Warning HostAssistedCloneSourceInUse 4m42s (x11 over 4m44s) datavolume-controller pod openshift-virtualization-os-images/size-detection-ae130582-c792-4677-86dd-f78c8c243ee8 using PersistentVolumeClaim fedora-56ccabc01cbe

      cdi deployment pod log:
      {"level":"debug","ts":1670816776.3534229,"logger":"events","msg":"Normal","object":

      {"kind":"DataVolume","namespace":"default","name":"clone4","uid":"349bdb29-09e6-4a0a-9ade-ee4ac4582ade","apiVersion":"cdi.kubevirt.io/v1beta1","resourceVersion":"10785711"}

      ,"reason":"SizeDetectionPodNotReady","message":"The size detection pod is not finished yet"}
      {"level":"debug","ts":1670816776.3534684,"logger":"events","msg":"Warning","object":

      {"kind":"DataVolume","namespace":"default","name":"clone4","uid":"349bdb29-09e6-4a0a-9ade-ee4ac4582ade","apiVersion":"cdi.kubevirt.io/v1beta1","resourceVersion":"10785711"}

      ,"reason":"HostAssistedCloneSourceInUse","message":"pod openshift-virtualization-os-images/size-detection-ae130582-c792-4677-86dd-f78c8c243ee8 using PersistentVolumeClaim fedora-56ccabc01cbe"}

      Expected results:
      Better to have a more friendly error when missing storage size in clone
      such as: missing storage size in DataVolume

      Additional info:

              rh-ee-alromero Alvaro Romero
              yadu1@redhat.com Yan Du
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: