Bug 1149809 - Faulty storage allocation checks when running VM with unplugged disks as stateless
Summary: Faulty storage allocation checks when running VM with unplugged disks as stat...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.5.1
Assignee: Vered Volansky
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On:
Blocks: 1054175 1178022 1193195
TreeView+ depends on / blocked
 
Reported: 2014-10-06 16:32 UTC by Vered Volansky
Modified: 2016-02-10 16:53 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
: 1178022 (view as bug list)
Environment:
Last Closed: 2015-01-12 13:00:06 UTC
oVirt Team: Storage
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33800 0 master MERGED core: RunVmValidator storage allocation Never
oVirt gerrit 33876 0 ovirt-engine-3.5 MERGED core: RunVmValidator storage allocation Never

Description Vered Volansky 2014-10-06 16:32:08 UTC
Description of problem:
Looking into the code, this verification was done with all disks, while it should have been done with only plugged disks.

Run a VM as stateless with and without plugged disks, and with and without storage space for new disks.

No plugged disks - CDA should pass - even when there's low storage space.
plugged disks - CDA should fail when there's not enough space for the plugged disks only.

      | 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)

Comment 1 Vered Volansky 2015-01-12 13:00:06 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1178022#c3 as to why this is closed.


Note You need to log in before you can comment on or make changes to this bug.