Bug 1321415

Summary:	glusterfs-georep logrotate errors
Product:	Red Hat Enterprise Linux 6	Reporter:	Orion Poplawski <orion>
Component:	glusterfs	Assignee:	sankarshan <sankarshan>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	paulds
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:	2017-12-06 10:53:02 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 Orion Poplawski 2016-03-26 14:27:53 UTC

Description of problem:

cron.daily email reports:

/etc/cron.daily/logrotate:

error: glusterfs-georep:31 glob failed for /var/log/glusterfs/geo-replication-slaves/*/*.log: No such file or directory
error: found error in file glusterfs-georep, skipping

Version-Release number of selected component (if applicable):
glusterfs-3.6.0.55-1.el6.x86_64

I'm not actively running glusterfs, it's being brought in as a dependency of qemu-kvm.

I suppose it's possible that this is a bug in logrotate not handling missingok in conjunction with multiple *'s.

Comment 2 Paul Stauffer 2016-04-20 13:42:48 UTC

This was fixed in 3.7.  See Bug 1170825 for details.  But yeah, Red Hat might want to update their 3.6.x packages for RHEL 6 to correct this.

Comment 3 Jan Kurik 2017-12-06 10:53:02 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/