Bug 818712

Summary:	log messages for configuration errors should be more clear
Product:	[Retired] oVirt	Reporter:	Dennis Jacobfeuerborn <dennisml>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	abaron, acathrow, bazulay, dfediuck, dyasny, iheim, mgoldboi, ykaul
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:	2013-02-03 12:25:29 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 Dennis Jacobfeuerborn 2012-05-03 18:54:44 UTC

On the mailing list a user had a problem that resulted in the following log message:

MainThread::DEBUG::2012-05-03 11:22:33,866::vdsm-reg-setup::73::root::validate end. return: False

According to Doron Fediuck this means there is an error in the configuration file /etc/vdsm-reg/vdsm-reg.conf [1] but for a regular user this is not really clear from the log message.

The message should contain a clear hint that this is a configuration issue. Also it seems this is only logged as a DEBUG message when a broken configuration should really result in an ERROR or at least in a WARNING.


[1] http://lists.ovirt.org/pipermail/users/2012-May/001866.html

Comment 1 Itamar Heim 2013-02-03 12:25:29 UTC

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.