/var/log/ on nodes is being polluted over time, and it’s root partition

Bug #1318517 reported by Mike Scherbakov on 2014-05-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Bogdan Dobrelya

Bug Description

Not all logs are being rotated to master node, and we still have increasing of /var/ in size over time. It means that without periodical clean up, we can face a situation when node gets stuck. In case with controller it would mean stopping of operability of the whole OpenStack environment, as our HA architecture doesn’t yet allow to handle such kind of situation, and failover won’t happen. In case with compute node, it may lead to deniel in hosting of new instances. I’m not sure if it can influence already running kvm processes.

Let’s think what would the best approach here, should we have only /var/log/ LVM? Should we enable periodical clean up by cron?

Changed in fuel:
importance: Undecided → High
milestone: none → 5.1
status: New → Confirmed
assignee: Fuel Library Team (fuel-library) → Bogdan Dobrelya (bogdando)
Bogdan Dobrelya (bogdando) wrote :

I believe we should address all Logs Storage considerations including LVM ones. See https://blueprints.launchpad.net/fuel/+spec/manage-logs-with-free-space-consideration

Vladimir Kuklin (vkuklin) wrote :

this bug requires logs managing blueprint

Bogdan Dobrelya (bogdando) wrote :

As far as related BP targeted to 6.0 release we should retarget this issue as well

Changed in fuel:
milestone: 5.1 → 6.0
Bogdan Dobrelya (bogdando) wrote :
Changed in fuel:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers