yahoo-eng-team team mailing list archive

[Armando Migliaccio <1182704@xxxxxxxxxxxxxxxxxx>]

IMO the majority of the cases will see the agent run outside a virtual
environment; for cases where the agent does run in virtual env, setting
the PATH or using a symlink sounds preferable to me than adding a config
variable.

** Changed in: neutron
       Status: New => Opinion

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

Title:
  quantum-ns-metadata-proxy path is not configurable

Status in OpenStack Neutron (virtual network service):
  Opinion
Status in tripleo - openstack on openstack:
  Fix Released

Bug description:
  We are running quantum in a virtualenv, which means quantum-ns-
  metadata-proxy isn't on root's path; adjusting the filters etc is
  doable, but the netns command run has just 'quantum-ns-metadata-proxy'
  to execute, rather than allowing us to supply the full path.

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