Has nova-network been restarted? There was an issue where nova-network was signalling dnsmasq which would cause dnsmasq to stop responding to requests yet appear to be running fine.
You can see if killing dnsmasq, restarting nova-network, and rebooting an instance allows it to get a dhcp address again ... Nate On Jun 14, 2012 4:46 PM, "Christian Parpart" <tra...@gmail.com> wrote: > Hey all, > > I feel really sad with saying this, now, that we have quite a few > instances in producgtion > since about 5 days at least, I now have encountered the second instance > loosing its > IP address due to "No DHCPOFFER" (as of syslog in the instance). > > I checked the logs in the central nova-network and gateway node and found > dnsmasq still to reply on requests from all the other instances and it even > got the request from the instance in question and even sent an OFFER, as > of what > I can tell by now (i'm investigating / posting logs asap), but while it > seemed > that the dnsmasq sends an offer, the instances says it didn't receive one > - wtf? > > Please tell me what I can do to actually *fix* this issue, since this is > by far very fatal. > > One chance I'd see (as a workaround) is, to let created instanced retrieve > its IP via dhcp, but then reconfigure /etc/network/instances to continue > with > static networking setup. However, I'd just like the dhcp thingy to get > fixed. > > I'm very open to any kind of helping comments, :) > > So long, > Christian. > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
