Description of problem: When trying to implement log rotation for tcmu-runner logs, sending a HUP signal to tcmu-runner causes the service to terminate Version-Release number of selected component (if applicable): OCS Independent Mode glusterfs-server-3.12.2-47.el7rhgs.x86_64 vdsm-gluster-4.19.43-2.3.el7rhgs.noarch glusterfs-api-3.12.2-47.el7rhgs.x86_64 glusterfs-libs-3.12.2-47.el7rhgs.x86_64 glusterfs-fuse-3.12.2-47.el7rhgs.x86_64 glusterfs-rdma-3.12.2-47.el7rhgs.x86_64 gluster-nagios-common-0.2.4-1.el7rhgs.noarch python2-gluster-3.12.2-47.el7rhgs.x86_64 glusterfs-3.12.2-47.el7rhgs.x86_64 glusterfs-cli-3.12.2-47.el7rhgs.x86_64 gluster-nagios-addons-0.2.10-2.el7rhgs.x86_64 libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.2.x86_64 glusterfs-client-xlators-3.12.2-47.el7rhgs.x86_64 gluster-block-0.2.1-31.el7rhgs.x86_64 glusterfs-geo-replication-3.12.2-47.el7rhgs.x86_64 How reproducible: Every time Steps to Reproduce: 1. Implement the following logrotate config /etc/logrotate.d/tcmu-runner /var/log/tcmu-runner*.log { rotate 7 size 10M compress missingok notifempty nodateext postrotate /usr/bin/killall -HUP tcmu-runner > /dev/null 2>&1 || true endscript } 2. When the command /usr/bin/killall -HUP tcmu-runner > /dev/null 2>&1 || true is run manually for testing, both tcmu-runner and gluster-blockd services stop Actual results: tcmu-runner and gluster-blockd services terminate Expected results: tcmu-runner should respond properly to the HUP signal and allow the log to be rotated Additional info:
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 (OpenShift Container Storage 3.11.z 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-2020:5602