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

Bug 1618589

Summary: [Undercloud] logrotate configuration for openstack-heat doesn't contain copytruncate option
Product: Red Hat OpenStack Reporter: Keigo Noha <knoha>
Component: openstack-heatAssignee: Rabi Mishra <ramishra>
Status: CLOSED ERRATA QA Contact: Ronnie Rasouli <rrasouli>
Severity: medium Docs Contact:
Priority: low    
Version: 13.0 (Queens)CC: cyril, mburns, ramishra, sbaker, shardy, srevivo
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-heat-10.0.2-2.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-13 22:14:23 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:

Description Keigo Noha 2018-08-17 03:30:54 UTC
Description of problem:
logrotate configuration for openstack-heat doesn't contain copytruncate option in undercloud.

~~~
# cat openstack-heat 
/var/log/heat/*.log {
    rotate 14
    size 10M
    missingok
    compress
}
~~~

It causes the original file is not properly handled.
~~~
# lsof |grep /var/log/heat
heat-engi 21986                   heat    3w      REG              253,1  15529835  151021704 /var/log/heat/heat-engine.log-20180816 (deleted)
~~~

nova has copytruncate option in its conf file.
~~~
/var/log/nova/*.log {
    rotate 14
    size 10M
    missingok
    compress
    copytruncate
}
~~~

Version-Release number of selected component (if applicable):
openstack-heat-engine-10.0.1-2.el7ost.noarch

How reproducible:
Everytime

Steps to Reproduce:
1. Install Undercloud and run logrotate.
2.
3.

Actual results:
heat's log is not written to the new file after logrotation.

Expected results:
copytruncate avoids the situation.

Additional info:

Comment 11 errata-xmlrpc 2018-11-13 22:14:23 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, 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-2018:3603