Bug 1542466

Summary:	Traceback in vdsm.log: setBalloonTarget error=Balloon operation is not available
Product:	[oVirt] mom	Reporter:	Petr Kubica <pkubica>
Component:	General	Assignee:	Steven Rosenberg <srosenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Liran Rotenberg <lrotenbe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	0.5.11	CC:	bugs, lveyde, mavital, pkubica
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm v4.20.24	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:32:00 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:

Description Petr Kubica 2018-02-06 12:06:42 UTC

Description of problem:
In vdsm.log there shouldn't be any traceback.

vdsm[13451]: ERROR FINISH setBalloonTarget error=Balloon operation is not available
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 117, in method
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 678, in setBalloonTarget
return self.vm.setBalloonTarget(target)
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5223, in setBalloonTarget
raise exception.BalloonError(str(e))
BalloonError: Balloon operation is not available

Version-Release number of selected component (if applicable):
vdsm	        vdsm-4.20.17-1.el7ev.x86_64
libvirt	        libvirt-3.2.0-14.el7_4.7.x86_64
qemu-img-rhev  	qemu-img-rhev-2.9.0-16.el7_4.14.x86_64
glusterfs	glusterfs-3.8.4-54.el7.x86_64
vdsm-python	vdsm-python-4.20.17-1.el7ev.noarch
sanlock	        sanlock-3.5.0-1.el7.x86_64

Discovered during automation

Comment 1 Martin Sivák 2018-02-07 11:45:29 UTC

Can you please attach the VM's libvirt XML and logs? Was the balloon device enabled?

Comment 4 Liran Rotenberg 2018-04-15 10:56:29 UTC

Verified on:
vdsm-4.20.25-1.el7ev.x86_64
ovirt-engine-4.2.3-0.1.el7.noarch

Step of verification:
1. Create a VM
2. Disable Balloon device on the VM.
3. Run the VM.
4. Use memory hot-plug to add 5 times a 256MB of memory.

Result:
The traceback didn't show up in the vdsm log.

Comment 5 Sandro Bonazzola 2018-05-10 06:32:00 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.