Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1803778

Summary: Collectd-sensubility is missing in collectd container
Product: Red Hat OpenStack Reporter: Martin Magr <mmagr>
Component: openstack-containersAssignee: Jon Schlueter <jschluet>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 16.0 (Train)CC: amoralej, jjoyce, jschluet, lhh, lnatapov, m.andre, mburns, mrunge, oblaut, shrjoshi, slinaber, tvignaud
Target Milestone: z2Keywords: Triaged
Target Release: 16.0 (Train on RHEL 8.1)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-collectd-container-16.0-84 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1745510 Environment:
Last Closed: 2020-05-14 14:35:33 UTC Type: ---
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: 1733257, 1745510    
Bug Blocks: 1744122    

Description Martin Magr 2020-02-17 12:49:16 UTC 
Can We please get collectd-sensubility inside the collectd container?
Comment 3 Jon Schlueter 2020-02-27 17:42:14 UTC 
Please get patch into tripleo-common or kolla directly for getting that included.
Comment 4 Martin Magr 2020-03-02 09:31:23 UTC 
Patch is in kolla for a long time already:

https://github.com/openstack/kolla/commit/057d605d9

It is still there in stable/train:

https://github.com/openstack/kolla/blob/stable/train/docker/collectd/Dockerfile.j2#L37

Not sure where I should patch tripleo-common to get the package in the container though.
Comment 6 Jon Schlueter 2020-03-06 02:48:22 UTC 
changes are in place now and will be part of next z-stream.
Comment 9 Leonid Natapov 2020-04-22 10:57:43 UTC 
collectd-sensubility included in the collectd container
Comment 11 errata-xmlrpc 2020-05-14 14:35:33 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-2020:2167