yahoo-eng-team team mailing list archive

[Miguel Angel Ajo <majopela@xxxxxxxxxx>]

Public bug reported:

The pid file path changes from %s.pid to %s/pid during juno, due to this
change:

https://github.com/openstack/neutron/commit/7f8ae630b87392193974dd9cb198c1165cdec93b
#diff-448060f24c6b560b2cbac833da6a143dL68

That means the l3-agent and dhcp-agent (when isolated metadata is enabled) 
will respawn a second neutron-ns-metadata proxy on each namespace/resource
after upgrade (I->J) and agent restart due the inability to find the old PID
file and external process PID.

** Affects: neutron
     Importance: Undecided
     Assignee: Miguel Angel Ajo (mangelajo)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Miguel Angel Ajo (mangelajo)

** Description changed:

  The pid file path changes from %s.pid to %s/pid during juno, due to this
  change:
  
  https://github.com/openstack/neutron/commit/7f8ae630b87392193974dd9cb198c1165cdec93b
  #diff-448060f24c6b560b2cbac833da6a143dL68
  
- That means the l3-agent and dhcp-agent (when isolated metadata is enabled) will respawn a second
- neutron-ns-metadata proxy on each namespace/resource after upgrade (I->J) and agent restart
- due the inability to find the old PID file and external process PID.
+ That means the l3-agent and dhcp-agent (when isolated metadata is enabled) 
+ will respawn a second neutron-ns-metadata proxy on each namespace/resource
+ after upgrade (I->J) and agent restart due the inability to find the old PID
+ file and external process PID.

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

Title:
  Neutron agents won't pick up neutron-ns-metadata-proxy after I->J
  upgrade

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  The pid file path changes from %s.pid to %s/pid during juno, due to
  this change:

  https://github.com/openstack/neutron/commit/7f8ae630b87392193974dd9cb198c1165cdec93b
  #diff-448060f24c6b560b2cbac833da6a143dL68

  That means the l3-agent and dhcp-agent (when isolated metadata is enabled) 
  will respawn a second neutron-ns-metadata proxy on each namespace/resource
  after upgrade (I->J) and agent restart due the inability to find the old PID
  file and external process PID.

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