Bug 1796942 - The package collectd-write_http is missing in the collectd container
Summary: The package collectd-write_http is missing in the collectd container
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-containers
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: z12
: 13.0 (Queens)
Assignee: Chris Sibbitt
QA Contact: Marius Cornea
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-31 15:01 UTC by David Hill
Modified: 2023-10-06 19:06 UTC (History)
24 users (show)

Fixed In Version: openstack-collectd-container-13.0-115
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-24 17:35:01 UTC
Target Upstream Version:
Embargoed:
csibbitt: needinfo+
csibbitt: needinfo+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-13940 0 None None None 2022-03-15 04:48:27 UTC
Red Hat Knowledge Base (Solution) 4896901 0 None None None 2020-03-11 12:25:39 UTC
Red Hat Product Errata RHBA-2020:2738 0 None None None 2020-06-24 17:35:09 UTC

Internal Links: 1838364

Description David Hill 2020-01-31 15:01:10 UTC
Description of problem:
The package collectd-write_httpd is missing in the collectd container:

However, when collectd container tries to start we see the following error in the logs:
[2020-01-24 13:33:37] plugin_load: Could not find plugin "write_http" in /usr/lib64/collectd

$ sudo docker exec -it collectd rpm -qa | grep collectd
puppet-collectd-10.1.0-2.el7ost.noarch
collectd-ping-5.8.1-4.el7ost.x86_64
collectd-smart-5.8.1-4.el7ost.x86_64
collectd-hugepages-5.8.1-4.el7ost.x86_64
collectd-disk-5.8.1-4.el7ost.x86_64
collectd-ceph-5.8.1-4.el7ost.x86_64
collectd-connectivity-5.8.1-4.el7ost.x86_64
libcollectdclient-5.8.1-4.el7ost.x86_64
collectd-virt-5.8.1-4.el7ost.x86_64
collectd-snmp-agent-5.8.1-4.el7ost.x86_64
collectd-write_kafka-5.8.1-4.el7ost.x86_64
collectd-amqp1-5.8.1-4.el7ost.x86_64
collectd-ipmi-5.8.1-4.el7ost.x86_64
collectd-turbostat-5.8.1-4.el7ost.x86_64
collectd-sysevent-5.8.1-4.el7ost.x86_64
collectd-netlink-5.8.1-4.el7ost.x86_64
collectd-ovs-stats-5.8.1-4.el7ost.x86_64
collectd-procevent-5.8.1-4.el7ost.x86_64
collectd-ovs-events-5.8.1-4.el7ost.x86_64
python2-collectd-gnocchi-1.7.1-1.el7ost.noarch
collectd-utils-5.8.1-4.el7ost.x86_64
collectd-rdt-5.8.1-4.el7ost.x86_64
collectd-python-5.8.1-4.el7ost.x86_64
collectd-mysql-5.8.1-4.el7ost.x86_64
collectd-apache-5.8.1-4.el7ost.x86_64
collectd-5.8.1-4.el7ost.x86_64


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

How reproducible:
Always

Steps to Reproduce:
1. Try to enable write_http in the collectd container
2.
3.

Actual results:
Fails

Expected results:
Succeeds

Additional info:
The package collectd-write_httpd is missing in the collectd container

Comment 3 Martin Magr 2020-02-06 19:48:07 UTC
Looking at the case env config it might be a configuration problem, because according to [1]: Comments must be separated from other tokens by white space characters.

Eg. don't write:
  
  #CollectdExtraPlugins:
    #- write_http

but do write:

  # CollectdExtraPlugins:
    # - write_http

Or the parser could take the configuration as not commented. It is just a guess though ...  I would start there, because all the other parts of Director are ok. The /etc/collectd.d dir is purged before configuration and nowhere in the Director the plugin is being enabled.

Could you also paste here output of:

  grep -rn write_http /var/lib/config-data/puppet-generated/collectd/

[1] https://yaml.org/spec/1.2/spec.html#id2780069

Comment 4 Jose Castillo Lema 2020-02-13 13:04:50 UTC
Hi @Martin Magr!
The comments (#) were placed in order to disable write_http plugin, that is the opossite from what we are trying to accomplish here.
We are trying to activate it, as requested per IBM/NetCool.

The command requested:
[root@lab01csrkhw001 ~]# grep -rn write_http /var/lib/config-data/puppet-generated/collectd/
[root@lab01csrkhw001 ~]# 

Just to remember, write_http plugin is not activated right now, as Director deploy fails when it is activated as the packet collectd-write_httpd is missing in the collectd container.

Comment 5 Chris Sibbitt 2020-02-13 15:30:31 UTC
Jose, Martin was assisting with a workaround to correctly disable the configuration and allow for re-deployment as described on the attached support case (which is now closed).

The request for write_http has been triaged as a Future Feature, as it is not included in our currently supported container image. It will get targeted to a future release based on project management priorities.

I hope this helps to clarify the narrative on this bug.

Comment 6 Jose Castillo Lema 2020-02-13 19:55:02 UTC
Hi Chris,

understood.
But we believe this should be treated as bug and not as Future Feature.
This is not a new functionality, the write_http plugin is supposed to work and listed in our documentation (https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/service_telemetry_framework/appe-saf-collectd-plugins), and it will hopefully work normally once the packet collectd-write_httpd is included the collectd container.
Could we please proceed this way?

Thanks a lot,
Jose

Comment 7 Jose Castillo Lema 2020-02-13 20:07:39 UTC
Just to be sure we all in the same page,
the packet collectd-write_httpd is present in the RHEL image. The problem is that has not been mapped into the collectd container.
So, we believe a simple collectd image update should resolve the issue.

Thanks a lot,

Comment 9 Chris Sibbitt 2020-02-13 21:51:05 UTC
Okay, thanks for the additional clarification.

Comment 41 Leonid Natapov 2020-06-10 20:45:30 UTC
()[root@controller-0 /]# rpm -qa | grep http
collectd-write_http-5.8.1-5.el7ost.x86_64

Comment 43 errata-xmlrpc 2020-06-24 17:35:01 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:2738


Note You need to log in before you can comment on or make changes to this bug.