yahoo-eng-team team mailing list archive

[Eugene Nikanorov <enikanorov@xxxxxxxxxxxx>]

I believe this was fixed by introducing a check for process state (not only dnsmasq, but for ns-metadata-proxy as well).
Marking as Invalid.

** Changed in: neutron
     Assignee: Ante Karamatić (ivoks) => (unassigned)

** Changed in: neutron
       Status: In Progress => Invalid

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

Title:
  neutron doesn't check if dnsmasq is running before using it

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  Sometimes, for non-neutron related reasons, dnsmasq could go away (get
  killed or similar). Neutron doesn't check if dnsmasq is really running
  before relaying upon its functionality. If dnsmasq dies before
  instance is started, instance can not pick up the IP. While restarting
  the dhcp-agent would reslov the problem, I believe dhcp-agent should
  start dnsmasq if needed.

  Instance wihout dnsmasq running:

  cloud-init-nonet gave up waiting for a network device.
  ci-info: lo    : 1 127.0.0.1       255.0.0.0       .
  ci-info: eth0  : 1 .               .               fa:16:3e:0d:76:91
  route_info failed
  Waiting for network configuration...
  Waiting up to 60 more seconds for network configuration...

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