Uploaded image for project: 'Virtualization Strategy'
  1. Virtualization Strategy
  2. VIRTSTRAT-350

When datavolume import fails, show the image size request

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • CNV v4.14.0
    • Storage Platform
    • Product / Portfolio Work
    • False
    • Hide

      None

      Show
      None
    • False

      When trying to create a VM, select a qcow2 image to import, and specify the pvc size.

      When datavolume downloads image and sees that the size is too big for the pvc created, it throws an error:

      "DataVolume too small to contain image"

       

      However we don't know what the image size is, which means we need to download the image again manually to check (or try to find in the logs).

       

      In the importer pod logs , we do see something like:

       

      1 data-processor.go:255] Virtual image size 5368709120 is larger than the reported available storage 3408704204. A larger PVC is required.

       

      However this is not passed to the gui, or even 'oc describe' output.  It would be very useful for the user to know exactly what size is required, so they don't need to figure out by trial and error.

       

      In addition, there are some cases where an overhead is required, making it even more difficult to calculate an appropriate size.  For this instance, it would be especially useful to report the required size.

       

      https://docs.openshift.com/container-platform/4.15/virt/storage/virt-reserving-pvc-space-fs-overhead.html

              Unassigned Unassigned
              rhn-support-mwest Marcus West
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: