Neutron metadata proxy should be checked for liveness periodically

Bug #1257775 reported by Brian Haley
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Brian Haley

Bug Description

We've seen at least one occurrence where the metadata proxy in the namespace has died, leading to unusable instances since their metadata requests fail to get required objects such as ssh keys.

The l3-agent can easily check all of it's sub-processes are still running, I have a small patch that can do this, along with a configuration option to enable it so users can choose not to run it.

Changed in neutron:
assignee: nobody → Brian Haley (brian-haley)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/59997

Changed in neutron:
status: New → In Progress
Kyle Mestery (mestery)
Changed in neutron:
importance: Undecided → Low
milestone: none → icehouse-2
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-2 → icehouse-3
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-3 → icehouse-rc1
Revision history for this message
Mark McClain (markmcclain) wrote :

Seems like this is something worth reviving.

Changed in neutron:
milestone: icehouse-rc1 → none
Revision history for this message
Brian Haley (brian-haley) wrote :

Yes, agreed, I will update it for Juno as there are now some other things started from the l3-agent that probably want to be monitored as well.

Revision history for this message
Brian Haley (brian-haley) wrote :

This issue is now fixed in Kilo (or before?) with the ProcessMonitor changes in Neutron - the spawned metadata proxy is now "watched" and restarted if the user enables it. So this can be closed.

Revision history for this message
Miguel Angel Ajo (mangelajo) wrote :

Yes, this was fixed by Mike kolesnik or Assaf Muller I think.

Can't remember now.

Changed in neutron:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.