Bug 1796942
| Summary: | The package collectd-write_http is missing in the collectd container | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | David Hill <dhill> |
| Component: | openstack-containers | Assignee: | Chris Sibbitt <csibbitt> |
| Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 13.0 (Queens) | CC: | aenrique, alolivei, asimonel, bshephar, csibbitt, dprince, ealcaniz, efoley, jbadiapa, jschluet, lars, ldenny, lnatapov, m.andre, mburns, mcornea, mgarciac, mmagr, mrunge, nchandek, pveiga, rmccabe, sasun, slinaber |
| Target Milestone: | z12 | Keywords: | Triaged, ZStream |
| Target Release: | 13.0 (Queens) | Flags: | csibbitt:
needinfo+
csibbitt: needinfo+ |
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-collectd-container-13.0-115 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-06-24 17:35:01 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: | |||
|
Description
David Hill
2020-01-31 15:01:10 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
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. 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. 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 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, Okay, thanks for the additional clarification. ()[root@controller-0 /]# rpm -qa | grep http collectd-write_http-5.8.1-5.el7ost.x86_64 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 |