Bug 1665072

Summary:	On engine side add write_syslog collectd output plugin dependency
Product:	[oVirt] ovirt-engine	Reporter:	Shirly Radco <sradco>
Component:	Packaging.rpm	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.3.0	CC:	bugs, emarcus, lleistne, pnovotny, sradco
Target Milestone:	ovirt-4.3.1	Flags:	rule-engine: ovirt-4.3+ rule-engine: blocker+ lleistne: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.1.1	Doc Type:	Enhancement
Doc Text:	In this release, the write_syslog collectd plugin is now automatically installed on the system running the ovirt-engine service to provide metrics store support.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-26 07:19:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1667417
Bug Blocks:	1615974

Description Shirly Radco 2019-01-10 13:11:40 UTC

Description of problem:
In order to replace fluentd with rsyslog we require the new write_rsyslog collectd plugin on the engine and hosts/appliance. Related to bug #1615974

Comment 1 Sandro Bonazzola 2019-01-10 13:50:59 UTC

requested plugin is pending review on upstream collectd repository: https://github.com/collectd/collectd/pull/3019
There isn't an easy way to consume it for now.

Comment 4 Pavel Novotny 2019-03-22 12:16:08 UTC

Verified in ovirt-engine-4.3.2.1-0.1.el7.noarch.

collectd-write_syslog package is now in the engine dependencies.

# rpm -qR ovirt-engine | grep collectd
collectd
collectd-disk
collectd-postgresql
collectd-write_http
collectd-write_syslog

Comment 5 Sandro Bonazzola 2019-03-26 07:19:15 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 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.