Bug 1185614

Summary: faulty storage allocation checks when adding a vm to a pool
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Vered Volansky <vered>
Status: CLOSED ERRATA QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, amureini, ecohen, gklein, iheim, kgoldbla, lpeer, lsurette, rbalakri, Rhev-m-bugs, tnisan, yeylon, ylavi
Target Milestone: ---Keywords: ZStream
Target Release: 3.5.1Flags: ylavi: Triaged+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1179690 Environment:
Last Closed: 2015-04-28 18:45:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1179690    
Bug Blocks: 1193058, 1197441    

Comment 2 Kevin Alon Goldblatt 2015-03-08 14:25:28 UTC 
Verified as follows with 3.5.1 vt14:

Adding vms to N existing pool:  

Available space:     Space required:     Pool based on Template:     Result:                           Correct behavior Y/N
------------------------------------------------------------------------------------------------------------------
5g                   2g                  VM with BLOCK disks (Prealloc)        Passed                                 Y
5g                   10g                 VM with BLOCK disks (Prealloc)        Failed with Low space on Disk          Y

5g                   20mb                VM with FILE disks  (Prealloc)       Passed                                  Y


4g                   2g                  VM with BLOCK disks (Prealloc)      Failed with Low space on Disk            Y

4g                   20mb                VM with FILE disks  (Prealloc)       Failed with Low space on Disk           Y


Moving to verified!
Comment 3 errata-xmlrpc 2015-04-28 18:45:10 UTC 
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, 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://rhn.redhat.com/errata/RHSA-2015-0888.html