Description of problem: A storage domain committed size currently calculates the virtual size of each image in the domain, while this works correctly when dealing only with leaf images, the calculation is faulty when taking snapshots into consideration since a non active image size can not change thus the calculation has to take into consideration the actual size of the inactive images and the virtual size only of the active images, this with the exception of template images which are active but only their actual size should be taken into consideration since they are read only. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a VM with 10GB disk thinly provisioned, the committed size is 10GB 2. Take a snapshot of the VM with the disk included 3. Actual results: The committed size appears as 20GB (10GB virtual size of each image) Expected results: The committed size should appear as 10GB on a file domain (actual size of 0 of the base image and 10GB virtual size of the leaf image) or 11GB on a block domain (actual size of 1GB of the base image and 10GB virtual size of the leaf image) Additional info:
oVirt 3.5 has been released and should include the fix for this issue.