Bug 1325458

Summary:	logrotate-3.8.6-7: error renaming temp state file /var/lib/logrotate.status.tmp
Product:	Red Hat Enterprise Linux 7	Reporter:	Douglas Schilling Landgraf <dougsland>
Component:	logrotate	Assignee:	Kamil Dudka <kdudka>
Status:	CLOSED DUPLICATE	QA Contact:	qe-baseos-daemons
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	dougsland, fdeutsch, kdudka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-02 11:15:57 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 Douglas Schilling Landgraf 2016-04-08 21:25:08 UTC

Description of problem:

# cat /etc/redhat-release 
Red Hat Enterprise Virtualization Hypervisor release 7.2 (20160407.0.el7ev)

# rpm -qa | grep -i logrotate
logrotate-3.8.6-7.el7_2.x86_64

# /usr/sbin/logrotate /etc/vdsm/logrotate/vdsm
error: error renaming temp state file /var/lib/logrotate.status.tmp

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

Additional info:

- audit logs or setenforce 0 doesn't help
- filesystem in rw doesn't help
- If I use --state /var/lib/logrotate.status-alt 
- Looks like it needs a backport from: https://bugzilla.redhat.com/show_bug.cgi?id=1127415 and https://bugzilla.redhat.com/show_bug.cgi?id=1228531 and a fix into rwtab (for /var/lib).

Comment 2 Kamil Dudka 2016-07-01 09:20:47 UTC

Sorry for the late reply on this.  I am a new maintainer of logrotate.  Could you please provide some steps to reproduce it on a fresh RHEL-7 installation?

Comment 4 Kamil Dudka 2016-09-02 11:15:57 UTC

As I understand this bug report, it is a duplicate of bug #1272236.

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

Comment 5 Douglas Schilling Landgraf 2016-09-02 13:37:30 UTC

(In reply to Kamil Dudka from comment #4)
> As I understand this bug report, it is a duplicate of bug #1272236.
> 
> *** This bug has been marked as a duplicate of bug 1272236 ***

Yes, looks like the same, thanks for fixing.