Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 915869

Summary: Possible to make template from vm, if vm disk has no quota assigned.
Product: Red Hat Enterprise Virtualization Manager Reporter: Ondra Machacek <omachace>
Component: ovirt-engineAssignee: ofri <omasad>
Status: CLOSED NOTABUG QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.2.0CC: acathrow, dfediuck, dyasny, iheim, lpeer, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-28 09:13:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log none

Description Ondra Machacek 2013-02-26 16:50:06 UTC
Created attachment 703022 [details]
engine.log

Description of problem:


Version-Release number of selected component (if applicable):
sf7

How reproducible:
always

Steps to Reproduce:
1. Create quota.
2. Set DC to disabled mode.
3. Create vm with disk.
4. Set DC to enforced mode.
5. Make template from vm.
  
Actual results:
Template is created.

Expected results:
It should not be possible to create templates of virtual machines whose virtual disks do not have assigned quotas

Additional info:

Comment 1 Doron Fediuck 2013-02-27 07:44:12 UTC
Thanks for the report Ondra.
I must say I'm not fully convinced this is a real issue.
The reason is that having such a template, you'll be forced to allocate a quota to each newly create VM's disk each time a snapshot or copy will occur.

Having that said, I'll look into it to see the actual impact in terms of usability.

Comment 4 ofri 2013-02-28 09:13:51 UTC
If I understand you correctly, what you are describing is not a bug. 
Once the DC was moved to Enforced Quota mode we do not allow to create any new disks (consume new storage) without assigning them with a quota. But we still allow using old disks (which have no quota assigned). One can copy old disks or activate the VMs running with those disks. When coping the disk one will have to supply a quota to be assigned to the new copy (because new storage is being consumed). When moving old disks one will have to supply a quota to be assigned to the old disk (again, because new storage is being consumed). But as long as no new storage is consumed - the user is not forced to assign a quota. 
In The case you are describing the user will only be forced to assign a quota to the new copy (the one in the newly created template) but the old disk could remain with no quota.