openstack team mailing list archive

[Lars Kellogg-Stedman <lars@xxxxxxxxxxxxxxxx>]

On Thu, Oct 18, 2012 at 06:16:07PM +0100, Ronivon Costa wrote:
>    I have noticed a similar behaviour, for example when the switch/router is
>    rebooted. I am able to recover the communications with the VMs  restarting
>    nova network (no need to kill dnsmasq).

There are no network devices being rebooted here...and since we're
running in multi_host mode, both dnsmasq and the affected instances
are running *on the same physical system*.

It happened again last night -- which means we were without networking
on our instances for about seven hours -- and restarting nova-network
doesn't resolve the problem.  It is necessary to first kill dnsmasq
(and allow nova-network to restart it).

There are no errors being logged by dnsmasq; started just after 2AM,
all of the "DHCPREQUEST ..." traffic just stops, and the logs after
that point look like this:

Oct 19 02:02:34 stack-1 dnsmasq[32013]: read /etc/hosts - 2 addresses
Oct 19 02:02:34 stack-1 dnsmasq[32013]: read /var/lib/nova/networks/nova-br662.conf
Oct 19 02:02:35 stack-1 dnsmasq[32013]: read /etc/hosts - 2 addresses
Oct 19 02:02:35 stack-1 dnsmasq[32013]: read /var/lib/nova/networks/nova-br662.conf
Oct 19 02:03:12 stack-1 dnsmasq[32013]: read /etc/hosts - 2 addresses
Oct 19 02:03:12 stack-1 dnsmasq[32013]: read /var/lib/nova/networks/nova-br662.conf

...until I restart things.

-- 
Lars Kellogg-Stedman <lars@xxxxxxxxxxxxxxxx>  |
Senior Technologist                           | http://ac.seas.harvard.edu/
Academic Computing                            | http://code.seas.harvard.edu/
Harvard School of Engineering                 |
  and Applied Sciences                        |