Bug 2057577 - [RHOSP16.2] [rsyslog] Misleading characters in the generated 50_openstack_logs.conf
Summary: [RHOSP16.2] [rsyslog] Misleading characters in the generated 50_openstack_lo...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-23 16:06 UTC by Luca Davidde
Modified: 2022-03-29 08:16 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-22 16:16:56 UTC
Target Upstream Version:
Embargoed:
ldavidde: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1945075 1 high CLOSED [RHOSP16.1][rsyslog] - Miss configuration generated in 50_openstack_logs.conf on controller's 2024-10-01 17:53:28 UTC
Red Hat Bugzilla 1949673 1 medium CLOSED [RHOSP16.2] [rsyslog] Miss configuration generated in 50_openstack_logs.conf 2022-08-23 22:53:35 UTC
Red Hat Issue Tracker OSP-12844 0 None None None 2022-02-23 16:10:31 UTC

Comment 3 Luca Davidde 2022-03-02 08:49:32 UTC 
Hi, any news on that?
Please reach me if you have any comment
Comment 7 Chris Sibbitt 2022-03-02 16:27:54 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.
Comment 8 Matthias Runge 2022-03-22 16:16:56 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.