Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If we follow the openstack doc to configure the centralized log: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/logging_monitoring_and_troubleshooting_guide/index#installing-and-configuring-the-logs-service_osp , the configuration is a container in charge to logrotate files with a cron job and another container is in charge to send files to elasticsearch with rsyslog.

- because containers can't send a signal to a service in another one, logrotate is configured with "copytroncate"
- Is this option reliable ?
- The issue is that rsyslog stops sending msg to remote host once the rotation occurred.

- I found the option reopenOnTruncate="on" of rsyslog that solves the issue, but it is marked as experimental.
Is it supported/recommended ?

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

How reproducible:
always, outside of openstack

Steps to Reproduce:
1. configure imfile on a log file and omfwd to send it to remote host
2. rotate the log
3. 

Actual results:
Logs are not sent to remote anymore after the rotation

Expected results:
Logs sent to elasticsearch
The main question is: Is this configuration expected to work ?

Thank you !

Additional info: