Comment 13 for bug 973442

Currently (out of an nova-compute cluster of size ~80 with heavy usage) we find at least one or two compute nodes every day with this issue, requiring a 'killall dnsmasq; service nova-network restart' to fix the issue.