Description of problem: When attempting to migrate RH 8.4 VM from VMware using the MTV, migration fails with an error reporting that the PVC it created is not large enough to support migration: ----------------------------------- # virtctl image-upload dv rhel-8... PVC abc/rhel-8 not found DataVolume abc/rhel-8 created Waiting for PVC rhel-8 upload pod to be ready... Pod now ready Uploading data to https://*****.com unexpected return value 400, Saving stream failed: Virtual image size abc is larger than available size xyz (PVC size abc, reserved overhead 0.055000%). A larger PVC is required. ----------------------------------- The work-around is to manually grow the created PVC to 2x its size, just following the start of the migration plan. This allows the migration to "complete". The VM was migrated in an off state and guest agent was shown as installing. VM was started, then qemu-guest-agent installed. Version-Release number of selected component (if applicable): OCP 4.9.23 MTV 2.2 How reproducible: Consistently Actual results: Migration fails with insufficient storage error Expected results: Migration would succeed
> unexpected return value 400, Saving stream failed: Virtual image size 32212254720 is larger than available size 28254549012 (PVC size 32212254720, reserved overhead 0.055000%). A larger PVC is required. As you can see, a 30 GiB PVC has only ~26.3 GiB usable space, which is... not so much. It seems that Portworx needs more than 0.055% overhead. Anyway, I don't see any issue on OCP side, all volumes were provisioned and mounted to the right Pods. I a moving it to migration toolkit to make sure they did the overhead calculation right, I don't know where this 0.055% comes from. Perhaps they can document that some storage backends need more overhead + a way how to configure it.
This is related to filesystem overhead on the CNV import side so I am moving the bug into the CNV Product.
*** Bug 2059057 has been marked as a duplicate of this bug. ***
verified on cnv 4.9.4.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Virtualization 4.11.0 Images security and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6526