Bug 2204505

Summary: The logrotate config created by cephadm does not take into account tcmu-runner
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Raimund Sacherer <rsachere>
Component: CephadmAssignee: Adam King <adking>
Status: CLOSED ERRATA QA Contact: Mohit Bisht <mobisht>
Severity: medium Docs Contact: Akash Raj <akraj>
Priority: unspecified    
Version: 5.3CC: adking, akraj, cephqe-warriors, prprakas, sostapov, tserlin, vdas
Target Milestone: ---   
Target Release: 5.3z4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-16.2.10-185.el8cp Doc Type: Bug Fix
Doc Text:
.`tcmu-runner` no longer stops logging after its log file is rotated Previously, `tcmu-runner` was left out of the postrotate actions of the logrotate configuration that Cephadm generated for rotating the logs of Ceph daemons on the host. Due to this, `tcmu-runner` would eventually stop logging as proper signals were not sent to regenerate its log file, which is done for other Ceph daemons using the previously mentioned postrotate actions in the logrotate configuration. With this fix, `tcmu-runner` is added to the postrotate actions in the logrotate file that Cephadm deploys for rotation of Ceph daemons logs. `tcmu-runner` no longer stops logging after its log file is rotated.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-19 16:19:10 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: 2210690    

Comment 4 Scott Ostapovicz 2023-06-14 16:05:55 UTC
Missed the 5.3 z4 deadline.  Moving from z4 to z5.

Comment 12 errata-xmlrpc 2023-07-19 16:19:10 UTC
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 (Red Hat Ceph Storage 5.3 Bug Fix update), 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-2023:4213