Bug 1102549

Summary:	ERROR message was shown in vdsm.log on host when VM suspend by RHEVM
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	yinwei <wyin>
Component:	vdsm	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED ERRATA	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	bazulay, dsulliva, dyuan, eedri, gklein, iheim, lpeer, mavital, michal.skrivanek, mzhan, nyechiel, rhodain, shyu, tdosek, vfeenstr, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:	vdsm-4.16.7-1.el6ev	Doc Type:	Bug Fix
Doc Text:	Previously, VDSM reported an 'ERROR' level log message for the non-severe and common event of a guest virtual machine disconnecting from the communication channel. This can happen when a virtual machine reboots, shuts down, or gets suspended or migrated. Now, the message has been changed to an 'INFO' level log message.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-11 21:11:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1156162

Description yinwei 2014-05-29 07:55:45 UTC

Description of problem:
ERROR message was shown in vdsm.log on host when suspend by RHEVM.

Version-Release number of selected component (if applicable):

libvirt-0.10.2-37.el6.x86_64
rhevm-3.3.3-0.52.el6ev.noarch
qemu-kvm-rhev-0.12.1.2-2.427.el6.x86_64
vdsm-4.13.2-0.17.el6ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. prepare an RHEVM server.

2. create date center,cluster,host.

3. create vm on host.
   notes: not install os.

4. chick suspend button.

5. check vdsm.log on host.
   #tail -f vdsm.log | grep ERROR

Actual results:
16:09:49,485::vmChannels::53::vds::(_handle_event) Received 00000019 on fileno 7

Expected results:
should not show ERROR message.

Additional info:
storage type:NFS,ISCSI.

Comment 1 Michal Skrivanek 2014-06-10 10:48:37 UTC

this is normal during VM life transitions.
since it's widespread enough I'd consider lesser importance (warn)

Comment 3 Vinzenz Feenstra [evilissimo] 2014-07-17 06:14:55 UTC

Merged to u/s master

LOGLEVEL is now INFO - For these issues it does not even make sense to WARN or report an ERROR. INFO is good enough when we need to investigate anything related.

Comment 4 Dave Sullivan 2014-09-26 15:35:04 UTC

Are we too late for 3.5?

Comment 6 Vinzenz Feenstra [evilissimo] 2014-09-28 06:13:07 UTC

(In reply to Dave Sullivan from comment #4)
> Are we too late for 3.5?

IMHO 3.5 RHEV should be still possible if it is important enough. It's not like that it is breaking anything.

Comment 7 Eyal Edri 2014-09-28 11:36:36 UTC

this bug was moved to MODIFIED before vt4 build date thus moving to ON_QA.
if you belive this bug isn't in vt4, please report to rhev-integ

Comment 8 Vinzenz Feenstra [evilissimo] 2014-09-29 07:24:10 UTC

This patch is not yet in the 3.5 branch. It has been moved from 3.6 to 3.5. The patch is still pending!

Comment 10 Nisim Simsolo 2014-10-22 13:57:48 UTC

Verified using:
vdsm-4.16.7-1.el6ev.x86_64
libvirt-0.10.2-46.el6.x86_64
sanlock-2.8-1.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64

Comment 12 errata-xmlrpc 2015-02-11 21:11:19 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-2015-0159.html