Bug 1392450

Summary:	[RFE] Upgrade collectd to version 5.6.1 or backport
Product:	Red Hat OpenStack	Reporter:	Shirly Radco <sradco>
Component:	collectd	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	dcadzow, lruzicka, mmagr, mrunge, nlevinki, parora, sclewis
Target Milestone:	Upstream M3	Keywords:	FeatureBackport, FutureFeature, Rebase, Triaged
Target Release:	11.0 (Ocata)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	collectd-5.7.0-4.el7ost	Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:	The new version of the collectd package (5.7.0) adds new features, the most notable being support for Ceph stats reporting and new options for the 'virt' plugin. The 'BlockDeviceFormat' and 'BlockDeviceFormatBasename' options help control the names reported for block device metrics. You are advised to upgrade to the newest version.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-17 20:24:21 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:
Bug Depends On:
Bug Blocks:	1402901

Description Shirly Radco 2016-11-07 14:21:15 UTC

Description of problem:
Collectd 5.5.2 has a max field length of 63 characters. The RHV team would like to use the collectd build for the next release, but this limit is too short.
The 5.6.1 version has a patch for this, the max is 128.

I see that a there is a build in Brew of Collectd 5.5.2 that imported this patch and built it, it-ops-rhel-7,
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=514720

Comment 4 Matthias Runge 2016-12-14 16:00:45 UTC

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

Comment 6 Leonid Natapov 2017-03-05 09:55:47 UTC

collectd-5.7.0-4.el7ost.x86_64

#define DATA_MAX_NAME_LEN 128

Comment 11 errata-xmlrpc 2017-05-17 20:24:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1246