W/o this patch, the most of the OCF agents
sending their own logs to nothere.
This is a major issue, because we want to
be able troubleshoot and keep OCF events
in syslog and collected at remote logs
server(s) as well.
The solution is to enable HA_LOGTAG and
HA_LOGFACILITY for each OCF script shipped
with the Fuel.
DocImpact: Ops guide. Logging events from
Fuel OCF agents will be collected both
locally in the /var/log/daemon.log and remotely,
with the file names based on the agent "foo-agent"
name as the "ocf-foo-agent.log". Note, that the
RabbitMQ will continue to log its OCF events
to the lrmd.log due to backwards compatibility reasons.
Reviewed: https:/ /review. openstack. org/215199 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=6d90814c567 5353aaf97946a40 eb92d55cb9bdb4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6d90814c5675353 aaf97946a40eb92 d55cb9bdb4
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Aug 20 17:31:53 2015 +0200
Fix missing OCF logging
W/o this patch, the most of the OCF agents
sending their own logs to nothere.
This is a major issue, because we want to
be able troubleshoot and keep OCF events
in syslog and collected at remote logs
server(s) as well.
The solution is to enable HA_LOGTAG and
HA_LOGFACILITY for each OCF script shipped
with the Fuel.
DocImpact: Ops guide. Logging events from agent.log" . Note, that the
Fuel OCF agents will be collected both
locally in the /var/log/daemon.log and remotely,
with the file names based on the agent "foo-agent"
name as the "ocf-foo-
RabbitMQ will continue to log its OCF events
to the lrmd.log due to backwards compatibility reasons.
Closes-bug: #1487083 31131e0f3a3e7b1 a771caf8dfd
Change-Id: Ida2d5fe31de42d
Signed-off-by: Bogdan Dobrelya <email address hidden>