Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1124764

Summary: extreme amount of irrelevant jsonrpc related log in vdsm log
Product: [Retired] oVirt Reporter: Nir Soffer <nsoffer>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: Gil Klein <gklein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5CC: acathrow, bazulay, ecohen, gklein, iheim, lsurette, mgoldboi, michal.skrivanek, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-30 10:43:17 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:
Attachments:
Description Flags
Output of "grep jsonrpc vdsm.log" none

Description Nir Soffer 2014-07-30 09:20:24 UTC
Created attachment 922472 [details]
Output of "grep jsonrpc vdsm.log"

Description of problem:

Looking in vdsm logs, we have too much noise related to how jsonrpc
server is implemented. These logs should be eliminated - the operation
of the server must be verified using unit tests, not by looking at the
logs.

See jsonrpc.log for json rpc related messages - most of them are have
no value for debugging application related issues.

Version-Release number of selected component (if applicable):
vdsm 4.16.1-0.gita4d9abf.fc19

Comment 1 Nir Soffer 2014-07-30 09:23:30 UTC
Expected logs when using jsonrpc:

- One debug log per connection
- One debug log for protocol detection
- One debug log when starting a request
- One debug log when finishing a request
- Errors and warnings

Comment 2 Michal Skrivanek 2014-07-30 10:43:17 UTC

*** This bug has been marked as a duplicate of bug 1124369 ***