Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1560210 - [RFE] Log Rotate in Podified Version Of CloudForms
[RFE] Log Rotate in Podified Version Of CloudForms
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: cfme-openshift-app (Show other bugs)
5.9.0
Unspecified Unspecified
unspecified Severity medium
: GA
: 5.9.2
Assigned To: Nick Carboni
Ievgen Zapolskyi
Red Hat CloudForms Documentation
: FutureFeature
: 1498970 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-24 18:37 EDT by Saif Ali
Modified: 2018-09-25 15:13 EDT (History)
7 users (show)

See Also:
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 09:50:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1329 normal SHIPPED_LIVE CloudForms 4.6.2 images for OpenShift bug fix and enhancement update 2018-05-07 21:51:48 EDT

  None (edit)
Description Saif Ali 2018-03-24 18:37:32 EDT
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 11:12:47 EDT
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 5 CFME Bot 2018-03-28 17:19:26 EDT
New commit detected on ManageIQ/manageiq-pods/gaprindashvili:

https://github.com/ManageIQ/manageiq-pods/commit/af0259e64d5ab8e5ea1bd49b348661994af6c68e
commit af0259e64d5ab8e5ea1bd49b348661994af6c68e
Author:     Nick Carboni <ncarboni@redhat.com>
AuthorDate: Tue Mar 27 12:08:09 2018 -0400
Commit:     Nick Carboni <ncarboni@redhat.com>
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 07:16:57 EDT
Verified in 5.9.2.3.
Comment 7 Nick Carboni 2018-04-30 15:47:45 EDT
*** Bug 1498970 has been marked as a duplicate of this bug. ***
Comment 10 CFME Bot 2018-09-25 15:13:37 EDT
New commit detected on ManageIQ/manageiq-pods/hammer:

https://github.com/ManageIQ/manageiq-pods/commit/af0259e64d5ab8e5ea1bd49b348661994af6c68e
commit af0259e64d5ab8e5ea1bd49b348661994af6c68e
Author:     Nick Carboni <ncarboni@redhat.com>
AuthorDate: Tue Mar 27 12:08:09 2018 -0400
Commit:     Nick Carboni <ncarboni@redhat.com>
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(-)

Note You need to log in before you can comment on or make changes to this bug.