Bug 1560210

Summary:	[RFE] Log Rotate in Podified Version Of CloudForms
Product:	Red Hat CloudForms Management Engine	Reporter:	Saif Ali <saali>
Component:	cfme-openshift-app	Assignee:	Nick Carboni <ncarboni>
Status:	CLOSED ERRATA	QA Contact:	Ievgen Zapolskyi <izapolsk>
Severity:	medium	Docs Contact:	Red Hat CloudForms Documentation <cloudforms-docs>
Priority:	unspecified
Version:	5.9.0	CC:	cpelland, dluong, izapolsk, lavenel, pmcgowan, simaishi, yrudman
Target Milestone:	GA	Keywords:	FutureFeature
Target Release:	5.9.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.9.2.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-09 13:50:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	CFME Core	Target Upstream Version:
Embargoed:

Description Saif Ali 2018-03-24 22:37:32 UTC

Description of problem:
In the podified version of CloudForms we log application logs to persistent volume but we don't have any tools to rotate the logs and without the rotating the logs the volume keep growing until it volume run out of space which cause the pod to crash.

Version-Release number of selected component (if applicable):
4.6

How reproducible:
Run podified version of CloudForms 4.6 in OCP3.7 and let it run for some time, and then check the logs

Steps to Reproduce:
1.
2.
3.

Actual results:
the log files keep growing

Expected results:
the log file should get rotated by adding some kind config map to do that or if possible we can send the logs to the stdout to be managed by logging service like elasticsearch 

Additional info:

Comment 2 Nick Carboni 2018-03-27 15:12:47 UTC

This does seem to not be working as the free space check script doesn't work properly in the pods.

We would need to provide an altered version of the logrotate configuration which doesn't call the free space check for the pods.

Comment 3 CFME Bot 2018-03-27 16:22:23 UTC

https://github.com/ManageIQ/manageiq-pods/pull/278

Comment 5 CFME Bot 2018-03-28 21:19:26 UTC

New commit detected on ManageIQ/manageiq-pods/gaprindashvili:

https://github.com/ManageIQ/manageiq-pods/commit/af0259e64d5ab8e5ea1bd49b348661994af6c68e
commit af0259e64d5ab8e5ea1bd49b348661994af6c68e
Author:     Nick Carboni <ncarboni>
AuthorDate: Tue Mar 27 12:08:09 2018 -0400
Commit:     Nick Carboni <ncarboni>
CommitDate: Tue Mar 27 12:08:09 2018 -0400

    Remove the check for filesystem space from the logrotate configuration

    This doesn't work in containers and was causing logrotate not to
    run for any log files.

    https://bugzilla.redhat.com/show_bug.cgi?id=1560210

 images/miq-app/container-assets/miq_logs.conf | 3 -
 1 file changed, 3 deletions(-)

Comment 6 Ievgen Zapolskyi 2018-04-26 11:16:57 UTC

Verified in 5.9.2.3.

Comment 7 Nick Carboni 2018-04-30 19:47:45 UTC

*** Bug 1498970 has been marked as a duplicate of this bug. ***

Comment 10 CFME Bot 2018-09-25 19:13:37 UTC

New commit detected on ManageIQ/manageiq-pods/hammer:

https://github.com/ManageIQ/manageiq-pods/commit/af0259e64d5ab8e5ea1bd49b348661994af6c68e
commit af0259e64d5ab8e5ea1bd49b348661994af6c68e
Author:     Nick Carboni <ncarboni>
AuthorDate: Tue Mar 27 12:08:09 2018 -0400
Commit:     Nick Carboni <ncarboni>
CommitDate: Tue Mar 27 12:08:09 2018 -0400

    Remove the check for filesystem space from the logrotate configuration

    This doesn't work in containers and was causing logrotate not to
    run for any log files.

    https://bugzilla.redhat.com/show_bug.cgi?id=1560210

 images/miq-app/container-assets/miq_logs.conf | 3 -
 1 file changed, 3 deletions(-)