yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: quantum
       Status: Fix Committed => Fix Released

** Changed in: quantum
    Milestone: havana-2 => havana-1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1183614

Title:
  Namespace metadata proxy runs without logging in devstack by default

Status in OpenStack Quantum (virtual network service):
  Fix Released

Bug description:
  The L3 agent is responsible for spawning the metadata proxy (quantum-
  ns-metadata-proxy), and at present only supports configuration of
  file-based logging for the proxy.  Even file-based logging will not be
  configured if log_dir is not set in the L3 agent config (see [1] and
  [2]).  This is the default in devstack, and the result is that the
  metadata proxy doesn't log anywhere, making any errors with the proxy
  opaque to a developer.

  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://github.com/openstack/quantum/blob/master/quantum/agent/l3_agent.py#L263
  [2] https://github.com/openstack/quantum/blob/master/quantum/agent/common/config.py#L40

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1183614/+subscriptions