Bug 1135939 - balloon is sent for PPC VMs
Summary: balloon is sent for PPC VMs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.4.1-1
Hardware: ppc64
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 3.4.3
Assignee: Jiri Moskovcak
QA Contact: Lukas Svaty
URL:
Whiteboard: sla
Depends On: 1127677
Blocks: 1122979
TreeView+ depends on / blocked
 
Reported: 2014-09-01 09:04 UTC by rhev-integ
Modified: 2016-02-10 20:14 UTC (History)
17 users (show)

Fixed In Version: org.ovirt.engine-root-3.4.3-2
Doc Type: Bug Fix
Doc Text:
Previously, when creating a virtual machine with 'ppc64' architecture, the 'Memory Balloon Device Enabled' check box was enabled, even though balloon is not supported on that architecture. This caused VM creation to fail. Now, the check box does not appear when 'ppc64' is selected, and no balloon request is sent.
Clone Of: 1127677
Environment:
Last Closed: 2014-10-23 12:30:20 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
engine.log (501.60 KB, application/x-gzip)
2014-10-03 10:43 UTC, Jiri Belka 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1712 0 normal SHIPPED_LIVE Red Hat Enterprise Virtualization Manager 3.4.3 update 2014-10-23 16:29:47 UTC
oVirt gerrit 31706 0 ovirt-engine-3.4 MERGED userportal, webadmin: don't enable balloon on ppc arch Never
oVirt gerrit 31753 0 master ABANDONED userportal | webadmin: don't enable balloon on ppc arch Never
oVirt gerrit 32038 0 master MERGED engine: don't allow to create VM with balloon on ppc64 Never
oVirt gerrit 32243 0 ovirt-engine-3.4 MERGED engine: don't allow to create VM with balloon on ppc64 Never
oVirt gerrit 33264 0 ovirt-engine-3.4 ABANDONED core: osinfo: add support for ballon device Never

Comment 2 Jiri Belka 2014-10-03 10:33:50 UTC 
2014-10-03 12:32:56,568 WARN  [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (ajp-/127.0.0.1:8702-5) [5a3d3aa] CanDoAction of action AddVmFromScratch failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__VM,BALLOON_REQUESTED_ON_NOT_SUPPORTED_ARCH,$clusterArch ppc64

rhevm-3.4.3-1.1.el6ev.noarch
Comment 3 Jiri Belka 2014-10-03 10:43:55 UTC 
Created attachment 943697 [details]
engine.log
Comment 4 Jiri Belka 2014-10-03 10:45:16 UTC 
Exact reproducer on 3.4.3:

1. new vm
2. select ppc clstr
3. put vm name
4. click enter

~~~
Error while executing action:

gggg:

    Cannot add VM. Balloon is not supported on 'ppc64' architecture.
~~~

no vm is created!
Comment 5 Jiri Belka 2014-10-03 11:41:29 UTC 
fyi in New VM -> Resource allocation there's no 'Memory Balloon Device Enabled' checkbox when ppc cluster is selected. So it's ok from UI perspective but balloon is still "loaded" in the background.
Comment 6 Michal Skrivanek 2014-10-03 12:24:35 UTC 
we're running out of time. Jiri, please update with investigation
Comment 7 Jiri Belka 2014-10-03 13:04:18 UTC 
workaround

curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" \
    -u admin@internal -k \
    -d "<vm><name>ppc64</name> \
    <cluster><name>ppc64</name></cluster> \
    <template><name>Blank</name></template> \
    <os type='rhel_6_ppc64'><boot dev='hd'/></os><memory_policy><ballooning>false</ballooning></memory_policy></vm>" \
    https://[engine]/api/vm
Comment 8 Jiri Moskovcak 2014-10-06 08:25:30 UTC 
(In reply to Michal Skrivanek from comment #6)
> we're running out of time. Jiri, please update with investigation

The problem was, that the first patch just hides the balloon checkbox, but it's value is still true. The second patch changes hides it & sets it to false.
Comment 9 Lukas Svaty 2014-10-14 11:27:50 UTC 
From the webadmin side this is VERIFIED.
However admin still needs to disable balloon manually when creating VM via other APIs. So this shout be set defaultly by engine. This will be tracked in BZ#1151599. If anybody thinks it should be tracked here re-open it.
Comment 11 errata-xmlrpc 2014-10-23 12:30:20 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-1712.html
Note You need to log in before you can comment on or make changes to this bug.