Bug 1300509

Summary: ironic should have its own log file
Product: [Community] RDO Reporter: Mohammed Arafa <bugzilla>
Component: openstack-ironicAssignee: Dmitry Tantsur <dtantsur>
Status: CLOSED EOL QA Contact: Toure Dunnon <tdunnon>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: Liberty   
Target Milestone: ---   
Target Release: Kilo   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 15:55:18 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 Mohammed Arafa 2016-01-21 03:22:18 UTC 
Description of problem:
ironic currently logs to /var/log/message as well as /var/log/ironic/*

this is 
a) causing garbage to appear in /var/log/messages
b) making it harder to identify non-ironic issues
c) making it harder to identify ironic  only issues
d) duplication
e) use of more disk space

the request is to keep ironic to its own log file

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Dmitry Tantsur 2016-01-21 09:04:33 UTC 
I think it's journalctl that puts something in /var/log/messages, not ironic itself, so I don't think we can do something about it, sorry.
Comment 2 Mohammed Arafa 2016-01-21 12:03:34 UTC 
have you seen the size of /var/log/messages? i was shocked to find it at 650M+
i had to edit my logrotate config to keep it at 10M

is there any workaround?
Comment 3 Dmitry Tantsur 2016-01-21 12:20:11 UTC 
I routinely work with 1.5-2 GiB logs from one service, so I know your feelings :) judging by https://fedoraproject.org/wiki/Changes/NoDefaultSyslog you have rsyslog installed, which causes /var/log/messages to be populated. I suspect uninstalling it will do the trick.
Comment 4 Chandan Kumar 2016-05-19 15:55:18 UTC 
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.