Bug 1349382 - Configuring Ballooning device for VM pools from SDK does not work
Summary: Configuring Ballooning device for VM pools from SDK does not work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.7
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Tomas Jelinek
QA Contact: Liran Rotenberg
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-23 11:16 UTC by Barak Korren
Modified: 2017-12-20 11:44 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:44:15 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)
reproducing script (1.95 KB, text/x-python)
2016-06-23 11:16 UTC, Barak Korren 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 79428 0 master MERGED restapi: respect the memory ballooning setting on new pool 2017-07-17 09:02:29 UTC

Description Barak Korren 2016-06-23 11:16:35 UTC 
Created attachment 1171430 [details]
reproducing script

Description of problem:
When creating a VM pool from the SDK, the ballooning device for the pool VMs gets configured as 'disabled' no matter what is passed on the VM parameters structure

Version-Release number of selected component (if applicable):
engine: 3.6.7-0.1.el6
sdk: 3.6.2.1-2

How reproducible:
A reproducing script attached
Comment 1 Ondra Machacek 2016-06-23 12:26:37 UTC 
Can you please enable debug, and send debug log of your script?

You can enable debug as follows:

 ...
 ovirt = API(
    url='engine.example.com',
    username='admin@internal',
    password='password',
    insecure=True,
    debug=True,
 )
 ...
Comment 2 Juan Hernández 2016-06-23 14:14:36 UTC 
The problem is in the engine, as it doesn't accept or report the ballooning element. Once it is fixed in the engine the SDK will work correctly without any modification.

*** This bug has been marked as a duplicate of bug 1348468 ***
Comment 3 Shahar Havivi 2016-06-28 10:59:35 UTC 
Reopening, since bz1348468 fix the fetching of the device,
This bug should fix setting the values in the engine as well in the api
Comment 4 Barak Korren 2016-07-04 13:45:42 UTC 
removing needinfo as all info was probably gathered elsewhere
Comment 5 Yaniv Kaul 2017-10-15 08:50:18 UTC 
Can this be moved to MODIFIED, or additional patches are expected?
Comment 6 Tomas Jelinek 2017-10-19 07:51:08 UTC 
thats all
Comment 7 Liran Rotenberg 2017-10-31 11:36:03 UTC 
Verified on:
4.2.0-0.0.master.20171025204923.git6f4cbc5.el7.centos

Steps of verification:
1. Run the script attached.

Result:

Script output:
Adding VM with Ballooning enabled
Adding VM with Ballooning disabled
Adding VM pool with Ballooning enabled
Adding VM pool with Ballooning disabled
Printing which VM has what:
balltest_pool_with-1     4294967296 2147483648 True
balltest_pool_without-1  4294967296 2147483648 False
balltest_vm_with         4294967296 2147483648 True
balltest_vm_without      4294967296 2147483648 False

The ballooning device for the pool VMs gets configured as it passed on the VM parameters structure.
Comment 8 Sandro Bonazzola 2017-12-20 11:44:15 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.