openstack team mailing list archive

[Thomas Kärgel <kaergel@xxxxxxxxxxxxx>]

Hi Johanna,

I'm facing the same behavior on a Folsom-installation on SLES11SP2. I
noticed that new hosts have correct entries in the dnsmasq config-files.
The dnsmasq processes get a HUP signal by DHCP-Agent, but simply refuse
to deliver the new address. Instead dnsmasq logs claim "no address
available". Exactly like in your description.
What distrubtion and exact dnsmasq-versions are in use on your environment?
I assume dnsmasq is not rereading its configs correctly on signal HUP.
dnsmasq logs claim it has reread configs, but it still does not deliver
the new adresses in host-file.
Manually trying to sigHUP dnsmasq had no effect. The only way to get out
of this state seems to be restarting DHCP-agent.

Best regards
Thomas

Am 20.05.2013 08:51, schrieb Heinonen, Johanna (NSN - FI/Espoo):
> Hi,
>  
> I have installed grizzly with quantum and ovs-plugin. It seems that
> grizzly allocates the third address of each subnet for dhcp. (In folsom
> it was the second address). This means that the VMs will get addresses
> .2, .4, .5, …
>  
> In my setup the first VM always boots fine and gets the address x.x.x.2.
> This can be seen in the syslog:
>  
> May 20 08:29:23 grizzly-236 dnsmasq-dhcp[2190]:
> DHCPDISCOVER(tapdbcef145-f5) 10.0.2.15 fa:16:3e:2d:0d:e0
> May 20 08:29:23 grizzly-236 dnsmasq-dhcp[2190]:
> DHCPOFFER(tapdbcef145-f5) 10.20.30.2 fa:16:3e:2d:0d:e0
> May 20 08:29:23 grizzly-236 dnsmasq-dhcp[2190]:
> DHCPREQUEST(tapdbcef145-f5) 10.20.30.2 fa:16:3e:2d:0d:e0
> May 20 08:29:23 grizzly-236 dnsmasq-dhcp[2190]: DHCPACK(tapdbcef145-f5)
> 10.20.30.2 fa:16:3e:2d:0d:e0 10-20-30-2
>  
> The problem comes when I start the second VM. Nova shows that the
> x.x.x.4 is allocated
>  
> root@grizzly-236:~# nova list
> +--------------------------------------+----------+--------+------------------------+
> | ID                                   | Name     | Status |
> Networks               |
> +--------------------------------------+----------+--------+------------------------+
> | c112ccbb-5039-4d05-b414-b53a1eafa2d8 | q-test   | ACTIVE |
> tenant1-net=10.20.30.2 |
> | 4f26975c-995d-403d-88b0-e7bbf189baad | q-test-2 | ACTIVE |
> tenant1-net=10.20.30.4 |
> +--------------------------------------+----------+--------+------------------------+
>  
> But from syslog I see that the answer to the DHCPDISCOVER is “no address
> available”
>  
> May 20 08:33:34 grizzly-236 dnsmasq-dhcp[2190]:
> DHCPDISCOVER(tapdbcef145-f5) 10.0.2.15 fa:16:3e:fc:1f:9a no address
> available
> May 20 08:33:52 grizzly-236 dnsmasq-dhcp[2190]:
> DHCPDISCOVER(tapdbcef145-f5) 10.0.2.15 fa:16:3e:fc:1f:9a no address
> available
>  
> When I restart the quantum-dhcp-server the problem disappears. This can
> be seen from the syslog:
>  
> May 20 09:01:40 grizzly-236 dnsmasq[7235]: started, version 2.59
> cachesize 150
> May 20 09:01:40 grizzly-236 dnsmasq[7235]: compile time options: IPv6
> GNU-getopt DBus i18n DHCP TFTP conntrack IDN
> May 20 09:01:40 grizzly-236 dnsmasq[7235]: warning: no upstream servers
> configured
> May 20 09:01:40 grizzly-236 dnsmasq-dhcp[7235]: DHCP, static leases only
> on 10.20.30.0, lease time 2m
> May 20 09:01:40 grizzly-236 dnsmasq[7235]: cleared cache
> May 20 09:01:40 grizzly-236 dnsmasq-dhcp[7235]: read
> /var/lib/quantum/dhcp/e6f27330-be41-478c-b4d2-49ed4ce0af00/host
> May 20 09:01:40 grizzly-236 dnsmasq-dhcp[7235]: read
> /var/lib/quantum/dhcp/e6f27330-be41-478c-b4d2-49ed4ce0af00/opts
> May 20 09:02:19 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPREQUEST(tapdbcef145-f5) 10.20.30.2 fa:16:3e:2d:0d:e0
> May 20 09:02:19 grizzly-236 dnsmasq-dhcp[7235]: DHCPNAK(tapdbcef145-f5)
> 10.20.30.2 fa:16:3e:2d:0d:e0 lease not found
> May 20 09:02:19 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPDISCOVER(tapdbcef145-f5) fa:16:3e:2d:0d:e0
> May 20 09:02:19 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPOFFER(tapdbcef145-f5) 10.20.30.2 fa:16:3e:2d:0d:e0
> May 20 09:02:19 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPREQUEST(tapdbcef145-f5) 10.20.30.2 fa:16:3e:2d:0d:e0
> May 20 09:02:19 grizzly-236 dnsmasq-dhcp[7235]: DHCPACK(tapdbcef145-f5)
> 10.20.30.2 fa:16:3e:2d:0d:e0 10-20-30-2
>  
> *May 20 09:03:39 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPDISCOVER(tapdbcef145-f5) fa:16:3e:fc:1f:9a*
> *May 20 09:03:39 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPOFFER(tapdbcef145-f5) 10.20.30.4 fa:16:3e:fc:1f:9a*
> *May 20 09:03:39 grizzly-236 dnsmasq-dhcp[7235]:
> DHCPREQUEST(tapdbcef145-f5) 10.20.30.4 fa:16:3e:fc:1f:9a*
> *May 20 09:03:39 grizzly-236 dnsmasq-dhcp[7235]: DHCPACK(tapdbcef145-f5)
> 10.20.30.4 fa:16:3e:fc:1f:9a 10-20-30-4*
>  
>  
> What could be the problem? Have you seen similar behavior? If yes, how
> did you fix this?
>  
> Best regards,
> Johanna
>  
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 


-- 
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

Attachment: signature.asc
Description: OpenPGP digital signature