Bug 1448473

Summary:	[downstream clone - 4.1.2] getAllVmIoTunePolicies exceptions in VDSM
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	vdsm	Assignee:	Andrej Krejcir <akrejcir>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0.7	CC:	bazulay, bgraveno, dfediuck, lsurette, mavital, mgoldboi, srevivo, ycui, ykaul
Target Milestone:	ovirt-4.1.2	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:	1437375	Environment:
Last Closed:	2017-05-24 11:25:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1437375
Bug Blocks:

Description rhev-integ 2017-05-05 13:45:58 UTC

+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1437375 +++
======================================================================

Around VM lifecycle changes MOM calls are triggering exceptions in VDSM. AFAICT it doesn't have impact on how product works, but it does have impact on troubleshooting and it triggers customer false alerts

Example from journal, likely related to a live migration:

Mar 29 13:23:21 bl460-558 journal: vdsm jsonrpc.JsonRpcServer ERROR Internal server error#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 545, in _handle_request#012    res = method(**params)#012  File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 195, in _dynamicMethod#012    result = fn(*methodArgs)#012  File "/usr/share/vdsm/API.py", line 1358, in getAllVmIoTunePolicies#012    io_tune_policies_dict = self._cif.getAllVmIoTunePolicies()#012  File "/usr/share/vdsm/clientIF.py", line 447, in getAllVmIoTunePolicies#012    vm_io_tune_policies[v.id] = {'policy': v.getIoTunePolicy(),#012  File "/usr/share/vdsm/virt/vm.py", line 2772, in getIoTunePolicy#012    qos = self._getVmPolicy()#012  File "/usr/share/vdsm/virt/vm.py", line 2746, in _getVmPolicy#012    metadata_xml = self._dom.metadata(#012  File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 47, in __getattr__#012    % self.vmid)#012NotConnectedError: VM u'dbc70ee7-1625-4660-8931-2d0639f64748' was not started yet or was shut down

(Originally by michal.skrivanek)

Comment 3 rhev-integ 2017-05-05 13:46:10 UTC

This problem will also be solved by the caching of IO tune policies done in Bug 1435218.

(Originally by Andrej Krejcir)

Comment 4 rhev-integ 2017-05-05 13:46:14 UTC

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[FOUND CLONE FLAGS: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ]

For more info please contact: rhv-devops

(Originally by rhev-integ)

Comment 5 rhev-integ 2017-05-05 13:46:18 UTC

WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[FOUND CLONE FLAGS: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ]

For more info please contact: rhv-devops

(Originally by rhev-integ)

Comment 7 Artyom 2017-05-11 09:57:52 UTC

I checked VDSM log for last 5 days and did not saw any Traceback connected to the getAllVmIoTunePolicies.
Verified on vdsm-4.19.12-1.el7ev.x86_64

Comment 9 errata-xmlrpc 2017-05-24 11:25:16 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://access.redhat.com/errata/RHEA-2017:1281