Bug 1457193

Summary:	"libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
Product:	Red Hat Enterprise Linux 7	Reporter:	yafu <yafu>
Component:	libvirt	Assignee:	Erik Skultety <eskultet>
Status:	CLOSED DUPLICATE	QA Contact:	yafu <yafu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	dyuan, fjin, jsuchane, lizhu, rbalakri, xuzhang, yanqzhan, zpeng
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-28 14:38:13 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:

Description yafu 2017-05-31 09:48:49 UTC

Description of problem:
"libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4

Version-Release number of selected component:
libvirt-3.2.0-6.virtcov.el7.x86_64

How reproducible:
100%

Steps to reproduce:
1.Don't change log setting in /etc/libvirt/virtlog.conf,the default log_level is 3.

2.Stop libvirtd service
# systemctl stop libvirtd


3.# libvirtd --verbose
no output

4.Change log_level 2 or 4, the result is same with step 3.

Actual results:
"libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4

Expected results:
"libvirtd --verbose" can output verbose messages when log_level is 2/3/4.

Comment 2 yafu 2017-05-31 09:52:20 UTC

(In reply to yafu from comment #0)
> Description of problem:
> "libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
> 
> Version-Release number of selected component:
> libvirt-3.2.0-6.virtcov.el7.x86_64
> 
> How reproducible:
> 100%
> 
> Steps to reproduce:
> 1.Don't change log setting in /etc/libvirt/virtlog.conf,the default
> log_level is 3.
> 
Correct "/etc/libvirt/virtlogd.conf" to "/etc/libvirt/libvirtd.conf"

> 2.Stop libvirtd service
> # systemctl stop libvirtd
> 
> 
> 3.# libvirtd --verbose
> no output
> 
> 4.Change log_level 2 or 4, the result is same with step 3.
> 
> Actual results:
> "libvirtd --verbose" doesn't output verbose messages when log_level is 2/3/4
> 
> Expected results:
> "libvirtd --verbose" can output verbose messages when log_level is 2/3/4.

Comment 3 Jaroslav Suchanek 2017-06-02 10:11:42 UTC

I suspect this commit:
commit 94c465d0eb5cc3c0f6908a6b11fad83887ec0216
Author:     Erik Skultety <eskultet>
AuthorDate: Mon Oct 31 12:52:51 2016 +0100
Commit:     Erik Skultety <eskultet>
CommitDate: Thu Dec 15 10:36:23 2016 +0100

    daemon: Hook up the virLog{Get,Set}DefaultOutput to the daemon's init routine
    
    Now that virLog{Get,Set}DefaultOutput routines are introduced we can wire them
    up to the daemon's logging initialization code. Also, change the order of
    operations a bit so that we still strictly honor our precedence of settings:
    cmdline > env > config now that outputs and filters are not appended anymore.
    
    Signed-off-by: Erik Skultety <eskultet>

Comment 4 Erik Skultety 2017-08-28 14:38:13 UTC


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