Bug 1155649 - [REST][CLI] Balloon on VM re-enabled on every API CALL for VM
Summary: [REST][CLI] Balloon on VM re-enabled on every API CALL for VM
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.4.3
Hardware: All
OS: Unspecified
medium
urgent
Target Milestone: ---
: 3.4.4
Assignee: Vitor de Lima
QA Contact: Lukas Svaty
URL:
Whiteboard: sla
Depends On: 1152991
Blocks: 1133612
TreeView+ depends on / blocked
 
Reported: 2014-10-22 14:32 UTC by Lukas Svaty
Modified: 2016-02-10 20:20 UTC (History)
16 users (show)

Fixed In Version: org.ovirt.engine-root-3.4.3-4
Doc Type: Bug Fix
Doc Text:
The REST API did not take into account of the current state of the ballooning device during the mapping of the incoming XML into an internal business entity. Instead of keeping the state of the ballooning device as it was before the API call, it was redefined as enabled. With this update, the REST API keeps the state of the ballooning device intact when a user omits any information about it in the incoming XML.
Clone Of: 1152991
Environment:
Last Closed: 2014-12-02 20:37:35 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1945 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.4.4 update 2014-12-03 01:37:09 UTC
oVirt gerrit 34208 0 master MERGED core, restapi,engine: Avoid enabling balloon device on VM edit Never
oVirt gerrit 34209 0 ovirt-engine-3.5 MERGED core, restapi,engine: Avoid enabling balloon device on VM edit Never

Comment 1 Lukas Svaty 2014-10-22 14:37:55 UTC 
WA for this is to add to every API CALL

<ballooning>false<ballooning>

In case this is missing in the API call balloon will be reenabled
Comment 2 Lukas Svaty 2014-11-10 16:36:22 UTC 
verified in av13
Comment 5 errata-xmlrpc 2014-12-02 20:37:35 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/RHBA-2014-1945.html
Note You need to log in before you can comment on or make changes to this bug.