AddVmPoolWithVmsCommand - VMs in the pool are added with empty disks (Thinly provisioned from the template). There are no memory volumes not snapshots. Storage allocation validation should be applied - StorageDomainValidator.HadSpaceForNewDisks(). Current validation is using old deprecated code. Verification of this bug should follow the following table: | 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) Verification should include a storage domain with and without enough space for all the vm (with disks) in the pool . In case of insufficient space a relevant CDA message should pop.
Since this is thinly provisioned, only sparse-qcow is in use here (from above table). Note in this flow the template already exist, so no allocation checks for it, and the allocation checks taken from the table above should be applied to all VMs (empty volume space* numOfVms).
This is an automated message: This bug should be fixed in oVirt 3.5.1 RC1, moving to QA
Verified downstream https://bugzilla.redhat.com/show_bug.cgi?id=1178021
oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.