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

Bug 1351247

Summary: Vdsm logging should be improved
Product: [oVirt] vdsm Reporter: Milan Zamazal <mzamazal>
Component: GeneralAssignee: Milan Zamazal <mzamazal>
Status: CLOSED NEXTRELEASE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.18.15CC: bugs, michal.skrivanek, mzamazal, sbonazzo, tjelinek
Target Milestone: ---Flags: rule-engine: planning_ack+
tjelinek: devel_ack+
mavital: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1361551 (view as bug list) Environment:
Last Closed: 2016-07-29 13:09:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1361551    

Description Milan Zamazal 2016-06-29 14:16:59 UTC
There are some problems with logging in Vdsm:

- Some RPC calls are not logged for various reasons, e.g. due to large parameters or responses.
- RPC calls are logged only on debug level.
- It's difficult to track status of all the VMs from the log.

Those problems should be fixed in order to get more complete information from the Vdsm log, even when the default logging level is set to INFO.

Comment 1 Michal Skrivanek 2016-07-01 12:16:08 UTC
since it's easily backportable and we critically need a better understanding of issues in existing deployments let's add it to next 3.6.z as well

Comment 2 Yaniv Kaul 2016-07-11 05:51:02 UTC
(In reply to Michal Skrivanek from comment #1)
> since it's easily backportable and we critically need a better understanding
> of issues in existing deployments let's add it to next 3.6.z as well

1. Is it in 4.0?
2. The Gerrit link shows it as merged, on July 1st. Since then, nothing happened to it for 3.6.z? Should it move to 3.6.9?

- Are we sure we are not flooding our log?

Comment 3 Milan Zamazal 2016-07-11 07:19:06 UTC
> 1. Is it in 4.0?

It has been merged to 4.0 branch.

> 2. The Gerrit link shows it as merged, on July 1st. 

This is probably the 4.0 merge.

> Since then, nothing happened to it for 3.6.z? Should it move to 3.6.9?

Patches for 3.6 are posted (I don't know why the tracker didn't add them), I was on PTO last week so there has been no progress from my side.

> - Are we sure we are not flooding our log?

In the patches, we address the problem of not flooding the log with allVmStats.

Comment 4 Sandro Bonazzola 2016-07-29 11:17:43 UTC
3.6 is gone EOL; Please re-target this bug to a 4.0 release.

Comment 5 Michal Skrivanek 2016-07-29 13:09:59 UTC
fix delivered in 4.0

Comment 6 Milan Zamazal 2016-07-29 13:22:39 UTC
Resolved, clearing needinfo.