Bug 1383655

Summary: Logrotate on rhev-h 7.2 cant write state file to /var/lib/ as it is read only
Product: Red Hat Enterprise Linux 7 Reporter: Marian Jankular <mjankula>
Component: logrotateAssignee: Kamil Dudka <kdudka>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2CC: kdudka
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-11 11:40:52 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:

Description Marian Jankular 2016-10-11 11:27:35 UTC 
Description of problem:
Logrotate on rhev-h 7.2 produces error in cron.log

Version-Release number of selected component (if applicable):
logrotate-3.8.6-7.el7_2.x86_64

How reproducible:
everytime on 7.2

Steps to Reproduce:
1.install rhevh 7.2 any version
2.connect to manager and leave running for some time (couple of hours)
3.check /var/log/cron.log for error messages
4. or just run logrotate manually instead of waiting

Actual results:
Oct  6 13:00:01 hv01 CROND[11797]: (root) CMDOUT (error: error creating output
file /var/lib/logrotate.status.tmp: Read-only file system


Expected results:
no error in syslog/cronlog

Additional info:
workaround:

modify /etc/cron.hourly/vdsm-logrotate line 
"/usr/sbin/logrotate /etc/vdsm/logrotate/vdsm"
to
"/usr/sbin/logrotate --state /tmp/vdsm_logrotate.state /etc/vdsm/logrotate/vdsm"
Comment 1 Kamil Dudka 2016-10-11 11:40:52 UTC 
I believe this is a duplicate of bug #1272236.

*** This bug has been marked as a duplicate of bug 1272236 ***