Bug 1037037

Summary:	Empty conf files cause exception
Product:	[Community] Publican	Reporter:	Jeff Fearn 🐞 <jfearn>
Component:	publican	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ruediger Landmann <rlandman>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2	CC:	aigao, norman, rlandman
Target Milestone:	4.1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.1.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-05 06:03:27 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:

Description Jeff Fearn 🐞 2013-12-03 02:58:55 UTC

Description of problem:
If you have any config file that is empty, or only comments, then publican dies at the attempt to load it. Publican also emits a default message and does not pass on the config modules error string.

1: If possible empty configs should be loaded without issue.

2: Any time that a config files fails to load the config modules error message should be passed on to the user.

Comment 2 Jeff Fearn 🐞 2014-02-23 23:20:46 UTC

*** Bug 1061434 has been marked as a duplicate of this bug. ***

Comment 3 Jeff Fearn 🐞 2014-03-20 01:57:25 UTC

I limited this change to only affect the brand default.cfg and overrides.cfg, all other cfg files that exist should not be empty.

To ssh://git.fedorahosted.org/git/publican.git
   1a4f78b..d6b2ed6  devel -> devel

Comment 4 Jeff Fearn 🐞 2014-05-05 06:03:27 UTC

A fix for this shipped in Publican 4.1.0.