yahoo-eng-team team mailing list archive

[norman shen <1988281@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

We are observing that neutron-dhcp-agent's state is deviating from "real
state", by saying real state, I mean all hosted dnsmasq are running and
configured.

For example, agent A is hosting 1,000 networks, if I reboot agent A then
all dnsmasq processes are gone, and dhcp agent will try to reboot every
dnsmasq, this will introduce a long delay between agent start and agent
handles new rabbitmq messages. But weirdly, openstack network agent list
will show that the agent is up and running which IMO is inconsistent. I
think under this situation, openstack network agent list should report
the corresponding agent to be down.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

- We are observing that neutron-dhcp-agent's state is deviating from "real state", by saying real state, I mean  
- all hosted dnsmasq are running and configured. For example, agent A is hosting 1,000 networks, if I reboot agent A then all dnsmasq processes are gone, and dhcp agent will try to reboot every dnsmasq, this will introduce a long delay between agent start and agent handles new rabbitmq messages. But weirdly, openstack network agent list will show that the agent is up and running which IMO is inconsistent.
+ We are observing that neutron-dhcp-agent's state is deviating from "real
+ state", by saying real state, I mean all hosted dnsmasq are running and
+ configured.
+ 
+ For example, agent A is hosting 1,000 networks, if I reboot agent A then
+ all dnsmasq processes are gone, and dhcp agent will try to reboot every
+ dnsmasq, this will introduce a long delay between agent start and agent
+ handles new rabbitmq messages. But weirdly, openstack network agent list
+ will show that the agent is up and running which IMO is inconsistent. I
+ think under this situation, openstack network agent list should report
+ the corresponding agent to be down.

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

Title:
  neutron  dhcp agent state not consistent with real status

Status in neutron:
  New

Bug description:
  We are observing that neutron-dhcp-agent's state is deviating from
  "real state", by saying real state, I mean all hosted dnsmasq are
  running and configured.

  For example, agent A is hosting 1,000 networks, if I reboot agent A
  then all dnsmasq processes are gone, and dhcp agent will try to reboot
  every dnsmasq, this will introduce a long delay between agent start
  and agent handles new rabbitmq messages. But weirdly, openstack
  network agent list will show that the agent is up and running which
  IMO is inconsistent. I think under this situation, openstack network
  agent list should report the corresponding agent to be down.

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