Bug 1585963 - Error in collectd 05-global-configuration.conf file - missing end of line
Summary: Error in collectd 05-global-configuration.conf file - missing end of line
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: Generic
Version: 1.1.4.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.4
: ---
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: 1581842
TreeView+ depends on / blocked
 
Reported: 2018-06-05 08:22 UTC by Shirly Radco
Modified: 2018-06-26 08:43 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-metrics-1.1.5.1-1.el7ev
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-26 08:43:46 UTC
oVirt Team: Metrics
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 91945 0 master MERGED Add EOL to collectd 05-global-configuration.conf file 2018-06-05 13:33:07 UTC

Description Shirly Radco 2018-06-05 08:22:38 UTC 
Description of problem:
Parsing error in collectd.d/05-global-configuration.conf because of missing end of line.

Parse error in file `/etc/collectd.d/05-global-configuration.conf', line 1827 near `': syntax error, unexpected $end


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

How reproducible:


Steps to Reproduce:
1. Configure metrics on host
2. Check journalctl -r -u collectd after service start
3.

Actual results:
Error message

Expected results:
No error

Additional info:
Comment 2 Lukas Svaty 2018-06-11 08:16:20 UTC 
verified in ovirt-engine-metrics-1.1.5.1-1.el7ev
Comment 3 Sandro Bonazzola 2018-06-26 08:43:46 UTC 
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.