Description of problem:
Install CNS 3.6 on top of OCP 3.6/7 and use e.g. dynamic provisioning for pods.
Logs get created below:
but normal glusterfs log-rotation (which gets automatically deployed) just take the following paths into consideration:
Version-Release number of selected component (if applicable):
- OCP 3.7
- CNS 3.6
Steps to Reproduce:
1. Install OCP with CNS on top
2. use gluster volumes
3. see logs growing in /var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/glusterfs/<vol-name>/*.log
logs never get rotated and fs usage grows, so manual interaction is needed
- we should add a rule automatically so that these logs get rotated
- and we should menation this in the documentation
possibly sth like
/usr/bin/killall -HUP glusterfs > /dev/null 2>&1 || true
/usr/bin/killall -HUP glusterd > /dev/null 2>&1 || true
seems to work, but I am pretty sure there are better solutions
- possibly someone can review my approach and make better suggestions so that I can file a kcs
Thanks for the bug, the path "/var/lib/origin/openshift.local.volumes/plugins/kubernetes.io/" belongs to openshift volume plugins and I believe it should be logrotated by openshift/origin. I will clone this bug so that we can track it.
Moving the bug to cns-deployment component. This will just be a tracker to the OCP bug that it depends on.
This ( how to do logrotate) can be documented for now, logs are in a common path for plugins. If this can be changed or not have to be discussed further and also may have to think about backward compatibility.
Bipin/Daniel, can anyone of you please help to create KCS and verify it in a CNS setup?
From https://bugzilla.redhat.com/show_bug.cgi?id=1546930#c5 :
manual logrotate config as a workaround
*** Bug 1546930 has been marked as a duplicate of this bug. ***