Bug 1338665

Summary:	Template of Glance imported VMs have Ballooning device disabled
Product:	[oVirt] ovirt-engine	Reporter:	Roman Mohr <rmohr>
Component:	BLL.Virt	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Carlos Mestre González <cmestreg>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.5.1	CC:	acanan, amureini, bugs, tjelinek, tnisan, ylavi
Target Milestone:	ovirt-4.0.0-rc	Flags:	rule-engine: ovirt-4.0.0+ rule-engine: planning_ack+ tnisan: devel_ack+ acanan: testing_ack+
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-05 08:01:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roman Mohr 2016-05-23 08:31:50 UTC

Description of problem:
When importing a VM image for instance via Glance, they have the field "Memory Balloon Device Enabled" unchecked. This is different than the default when creating a fresh VM from the default template.

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


How reproducible:
Always

Steps to Reproduce:
1. Import an image from glance as template
2. Check the "Resource Allocation" tab
3. "Memory Balloon Device Enabled" is disabled

Actual results:
VMs from the new tamplate are then created without ballooning device.

Expected results:
Having "Memory Balloon Device Enabled" checked by defualt, like in every other VM flow.

Additional info:

Comment 1 Michal Skrivanek 2016-05-24 08:25:09 UTC

The initial balloon setting is based on either the instance type (default ones have it disabled) or the selected template if no instance type is used, using "Blank" when you don't select any template

Tal, Import from Glance was a storage feature - was this intentional? If not then I suppose it could use "Blank" as well

Comment 2 Tal Nisan 2016-05-24 17:19:16 UTC

No, it was not done on purpose.
most of the settings are not set by default when importing from external provider but since it's a desired behavior I've changed it

Comment 3 Carlos Mestre González 2016-06-17 14:40:33 UTC

> Having "Memory Balloon Device Enabled" checked by defualt, like in every other VM flow.
This happens for the template and for the vms created from the template imported.

version: rhevm-4.0.0.4-0.1.el7ev.noarch

Comment 4 Sandro Bonazzola 2016-07-05 08:01:17 UTC

oVirt 4.0.0 has been released, closing current release.