← Back to team overview

openstack team mailing list archive

Re: DHCP problem in grizzly

 

Hi Thomas,
here you can find some logs required by dnsmasq devs.

http://paste.openstack.org/show/37668/

For this answer, "Maybe release a DHCP lease on an old host, and then see
if it can get a lease back again?" :
When the problem appears, the VM can't get lease back.

Should you have any further question please don't hesitate to contact me.
Thanks
Best Regards


2013/5/23 Thomas Kärgel <kaergel@xxxxxxxxxxxxx>

> Hi,
>
>  can somebody help to gather the desired informations? Since I'm not
> able to reproduce our problem i cannot answer Simons questions:
>
> >> The above mechanism is working fine in most cases. But lately there were
> >> a few reports (4 afaik) that this mechanism is not working entirely
> >> reliable.
> >> Dnsmasq re-reads it's configs but still claims that no address is
> >> available for the specific mac-address, while other clients are still
> >> receiving their adresses fine.
> >> The new entries in hostsfile do not get served until dnsmasq is killed
> >> and restarted.
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > This might be significant, since the process on re-read a hostfile is
> >
> > 1) Throw away all entries which came from a hostsfile in the past.
> > 2) Read the hostsfile and insert all the entries found there.
> >
> > It's difficult to see how that process could distinguish between new and
> old entries except if some hosts already have leases. Can you Explore this
> a bit more? Maybe release a DHCP lease on an old host, and then see if it
> can get a lease back again?
> >
>
> and...
>
> >> 10.20.30.2 fa:16:3e:2d:0d:e0 10-20-30-2
> >> May 20 09:04:34 grizzly-236 dnsmasq-dhcp[2190]:
> >> DHCPDISCOVER(tapdbcef145-f5) 10.0.2.15 fa:16:3e:fc:1f:9a no address
> >> available
> >> May 20 09:04:52 grizzly-236 dnsmasq-dhcp[2190]:
> >> DHCPDISCOVER(tapdbcef145-f5) 10.0.2.15 fa:16:3e:fc:1f:9a no address
> >> available
> >
> >
> > This is definitely "static address only on this network, unknown host"
> >
> >
> > It may be worth setting --log-dhcp for the extra information that can
> give us.
>
>
>
>
> Am 23.05.2013 09:35, schrieb Thomas Kärgel:
> > Hi,
> >
> > the bug report is open and can be viewed at:
> >
> http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q2/007212.html
> >
> > I used some of your logs in order to add more details to  my description.
> > Hopefully someone can help us solving this issue.
> >
> > Best regards
> > thomas
> >
>
>
> Bets regards
> thomas
> --
> Thomas Kärgel
> Linux Consultant
> Mail: kaergel@xxxxxxxxxxxxx
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
>
>


-- 
Marco Colombo

Follow ups

References