Bug 2142917
| Summary: | STF | Collectd deployed by tripleo-ansible fails to start because of the wrong path in collectd.conf file | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Leonid Natapov <lnatapov> | |
| Component: | tripleo-ansible | Assignee: | Chris Sibbitt <csibbitt> | |
| Status: | CLOSED UPSTREAM | QA Contact: | Leonid Natapov <lnatapov> | |
| Severity: | high | Docs Contact: | ||
| Priority: | low | |||
| Version: | 17.1 (Wallaby) | CC: | csibbitt, lmadsen, mmagr, mrunge | |
| Target Milestone: | ga | Keywords: | Triaged | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2143331 (view as bug list) | Environment: | ||
| Last Closed: | 2023-01-23 20:28:00 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: | 1872351, 2143331 | |||
|
Description
Leonid Natapov
2022-11-15 13:41:31 UTC
This bug was already fixed upstream: https://review.opendev.org/c/openstack/tripleo-ansible/+/831796/6/tripleo_ansible/roles/tripleo_collectd/tasks/configure_collectd.yml I think this bug should already be fixed in OSP 18. Here is the code in Wallaby (where the fix was never backported): https://opendev.org/openstack/tripleo-ansible/src/branch/stable/wallaby/tripleo_ansible/roles/tripleo_collectd/tasks/configure_collectd.yml#L225 Here it is in Zed: https://opendev.org/openstack/tripleo-ansible/src/branch/stable/zed/tripleo_ansible/roles/tripleo_collectd/tasks/configure_collectd.yml#L225 The difference is the '/' after collectd_conf_output_dir Closing this ticket as UPSTREAM. The fixes has landed upstream and will flow downstream appropriately. However, priority of this item is very low as it will not be recommended for production use, and thus will not work through the QE testing process. |