keystone messages no being written to syslog even when use-syslog=true
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystone (Juju Charms Collection) |
Fix Released
|
Medium
|
Leonardo Borda |
Bug Description
When setting use-syslog=true the [handler_
How to reproduce
1. deploy openstack from /openstack-
juju-deployer -c default.yaml -d trusty-kilo
juju deploy rsyslog rsyslog-primary
juju deploy rsyslog rsyslog-secondary
juju deploy rsyslog rsyslog-
# make the relations
juju add-relation rsyslog-
juju add-relation rsyslog-
2. juju service set keystone use-syslog=true
Solution
Change the following sections in charm-keystone/
Change the following sections in charm-keystone/
to
[logger_root]
{% if root_level -%}
level={{ root_level }}
{% else -%}
level=WARNING
{% endif -%}
handlers=
[handler_
class=handlers.
level=WARNING
formatter=
args=(('/dev/log'), handlers.
This covers the case where you have a local syslog daemon as well as a remote syslog daemon.
Changed in keystone (Juju Charms Collection): | |
assignee: | nobody → Leonardo Borda (lborda) |
Changed in keystone (Juju Charms Collection): | |
status: | New → In Progress |
summary: |
- charm-keystone doesn't log messages to syslog even when use-syslog=true + Ensure log-level config option is applied consistently in charm-keystone |
summary: |
- Ensure log-level config option is applied consistently in charm-keystone + keystone messages no being written to syslog even when use-syslog=true |
description: | updated |
Changed in keystone (Juju Charms Collection): | |
importance: | Undecided → Medium |
milestone: | none → 16.04 |
Changed in keystone (Juju Charms Collection): | |
status: | Fix Released → Fix Committed |
Changed in keystone (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/290632
Review: https:/