Description of problem: When powering off VM this traceback appears in mom: 2014-12-04 09:12:53,263 - mom.vdsmInterface - ERROR - {'status': {'message': 'Virtual machine does not exist', 'code': 1}} 2014-12-04 09:12:53,272 - mom.vdsmInterface - ERROR - Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py", line 146, in getVmBalloonInfo self._check_status(response) File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py", line 46, in _check_status raise vdsmException(response, self.logger) vdsmException 2014-12-04 09:12:53,272 - mom.vdsmInterface - ERROR - {'status': {'message': 'Virtual machine does not exist', 'code': 1}} 2014-12-04 09:12:53,272 - mom.vdsmInterface - ERROR - Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py", line 171, in getVmCpuTuneInfo self._check_status(response) File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmInterface.py", line 46, in _check_status raise vdsmException(response, self.logger) vdsmException Version-Release number of selected component (if applicable): mom-0.4.1-2.el7ev.noarch How reproducible: once a day maybe? :) Steps to Reproduce: 1. PowerOff VM 2. see mom.log on host Actual results: Traceback Expected results: Clean mom.log Additional info: Im not really sure of the reproduction steps. Mostly I was able to reproduce this with new host and first use, or not using host for some time (1 day) and then trying to Start and PowerOff VM on it. If I'll be able to reproduce and it will be really neccessary I can create and attach logs.
It's not actually a serious problem, it's a race we can't prevent. Mom gets the list of the VMs from vdsm and runs monitors for the guests. If user kills the vm after getting the list but before the monitor finishes, we get this exception. The proper fix here is to handle the exception in nicer way and just print a warning that the VM dissapeared while mom was processing it.
I am OK with this solution as this doesnt cause any flow isue. Cleaning the Traceback from log and giving some wargning is sufficient.
3.5.1 is already full with bugs (over 80), and since none of these bugs were added as urgent for 3.5.1 release in the tracker bug, moving to 3.5.2
Try to verify on : Red Hat Enterprise Virtualization Manager Version: 3.6.0.1-0.1.el6 The exception still appears..: 2015-10-20 09:45:19,668 - mom.Monitor - WARNING - golden_env_mixed_virtio_1: Collection error: Cannot read stat file: No such process 2015-10-20 09:45:19,684 - mom.Collectors.GuestMemory - WARNING - getVmMemoryStats() error: VM 8ed3defc-101d-4848-94d4-fd75a0908c2f does not exist 2015-10-20 09:45:19,684 - mom.Monitor - ERROR - Unexpected collection error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mom/Monitor.py", line 95, in collect collected = c.collect() File "/usr/lib/python2.7/site-packages/mom/Collectors/GuestBalloon.py", line 41, in collect stat = self.hypervisor_iface.getVmBalloonInfo(self.uuid) File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmxmlrpcInterface.py", line 178, in getVmBalloonInfo raise HypervisorInterfaceError("VM %s does not exist" % uuid) HypervisorInterfaceError: VM 8ed3defc-101d-4848-94d4-fd75a0908c2f does not exist 2015-10-20 09:45:19,684 - mom.Monitor - ERROR - Unexpected collection error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mom/Monitor.py", line 95, in collect collected = c.collect() File "/usr/lib/python2.7/site-packages/mom/Collectors/GuestCpuTune.py", line 44, in collect stat = self.hypervisor_iface.getVmCpuTuneInfo(self.uuid) File "/usr/lib/python2.7/site-packages/mom/HypervisorInterfaces/vdsmxmlrpcInterface.py", line 203, in getVmCpuTuneInfo raise HypervisorInterfaceError("VM %s does not exist" % uuid) HypervisorInterfaceError: VM 8ed3defc-101d-4848-94d4-fd75a0908c2f does not exist
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Closing old issues based on capacity. Please re-open only if relevant and needed.