The storage requirements for each disk in the imported template: For new empty disks (unchanged from the original) | File Domain | Block Domain -----|-----------------------------------------|------------- qcow | 1M (header size) | 1G -----|-----------------------------------------|------------- raw | preallocated: disk capacity (getSize()) | disk capacity | thin (sparse): 1M | (there is no raw sparse on block domains)
Disregard bug description (comment #0). The scenario is conducted through ImportVmTemplateFromConfigurationCommand. This is triggered by import a storage domain, where the disks already exist in the system, so just make sure there storage allocation tests always pass on this scenario.
In this command CDA verifications should never get to storage allocations. Moving straight to ON_QA. Fixed In Version: ovirt-3.5.0-beta2 What should be verified is that this command never fails on insufficient storage space when importing a vm template with disks. On registration the disks should already be on the storage domain, and they're only attached to the template. If the do not already exist on the storage domain, the vm template will be imported without the missing disks. 1. Create a VMTemplate with 7 disks, each disk 1 GB 2. Export the template 3. Detach the Storage Domain 4. Attach the Storage Domain to another DC 5. Activate it 6. Create disks on the Storage Domain until its free space is < 7 GB 7. Try to import the VMTemplate that you exported - Should fail on CDA 8. Try to register the VMTemplate - should succeed
verified using vt3.1 following steps in comment #2
oVirt 3.5 has been released and should include the fix for this issue.