Namespace metadata proxy runs without logging in devstack by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
yong sheng gong |
Bug Description
The L3 agent is responsible for spawning the metadata proxy (quantum-
Either a sane default should be provided to ensure that some kind of logging is always configured for the proxy, or the L3 agent (and the DHCP agent going forward) should error out when it realizes that it can't configure logging for the proxy.
[1] https:/
[2] https:/
description: | updated |
tags: | added: quantum-core |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
milestone: | havana-2 → havana-1 |
Changed in neutron: | |
milestone: | havana-1 → 2013.2 |
Maybe log at a warning level to syslog by default?