Bug 2057577
| Summary: | [RHOSP16.2] [rsyslog] Misleading characters in the generated 50_openstack_logs.conf | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Luca Davidde <ldavidde> |
| Component: | openstack-tripleo-heat-templates | Assignee: | OSP Team <rhos-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 16.2 (Train) | CC: | astupnik, csibbitt, ldavidde, mburns, mrunge |
| Target Milestone: | --- | Keywords: | Triaged, ZStream |
| Target Release: | --- | Flags: | ldavidde:
needinfo-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-03-22 16:16:56 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: | |||
|
Comment 3
Luca Davidde
2022-03-02 08:49:32 UTC
This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1949673 which is fixed, verified, and set to be released imminently as part of 16.2.2 Here is the patch which suggests the fix: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/785956/4/deployment/metrics/qdr-container-puppet.yaml I don't have an environment in front of me to check the rendering, but my reading of this is that you need to double-up the backslashes in the rsyslog config file (accomplished by the change of quotes in the patch). You also need to fix the path to the log file. If this successfully works around the rsyslog startup problem, then we can be pretty sure that the 16.2.2 update will fix it more permanently. Based on Chris' comment, this should be fixed by z2, which is supposed to be sent out on March 23rd. If this is not resolved in the next release, please reopen and we'll investigate. |