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
Can you please attach the VM's libvirt XML and logs? Was the balloon device enabled?
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.
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.