Bug 1502206 - Vdsm fails to start when logger conf file is invalid
Summary: Vdsm fails to start when logger conf file is invalid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.20.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.7
: 4.19.35
Assignee: Yaniv Bronhaim
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-15 08:12 UTC by Yaniv Bronhaim
Modified: 2017-11-13 12:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-13 12:26:10 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82446 0 master MERGED Change to Exception level from RuntimeError when treating logger conf 2017-10-16 08:06:21 UTC
oVirt gerrit 82789 0 ovirt-4.1 MERGED Change to Exception level from RuntimeError when treating logger conf 2017-10-16 15:26:01 UTC

Description Yaniv Bronhaim 2017-10-15 08:12:32 UTC 
The Exception level that we catch doesn't catch format errors in conf file.
This fix changes the RuntimeError to general Exception when treating logger conf.


Version-Release number of selected component (if applicable):
4.20.4

How reproducible:
100%

Steps to Reproduce:
1. invalid syntax in /etc/vdsm/logger.conf file
2. run vdsmd service
3.

Actual results:
starts normally but fails during run

Expected results:
fails to start with syslog notification


Additional info:
Comment 1 Petr Matyáš 2017-10-25 10:29:43 UTC 
Verified on vdsm-4.19.35-1.el7ev.x86_64
Note You need to log in before you can comment on or make changes to this bug.