<div dir="ltr">Could it be zeroconf? I think avahi-daemon in some cases adds that route; perhaps it's worth trying and stopping it.<div style><br></div><div style>Salvatore</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On 25 April 2013 08:15, Balamurugan V G <span dir="ltr"><<a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>Hi Leen,<br><br></div>I do not have any other DHCP sever which can do this other than the one created by quantum. Infact, If i delete the route manually and restart the network(interface down and up), I get the routed added back. Please refer below:<br>
<div><div><br>root@vm:/var/lib/dhcp# route -n<div class="im"><br>Kernel IP routing table<br>Destination Gateway Genmask Flags Metric Ref Use Iface<br></div><div class="im">0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0<br>
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0<br>192.168.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0<br></div>root@vm:/var/lib/dhcp# route del -net 169.254.0.0 netmask 255.255.0.0<br>
root@vm:/var/lib/dhcp# route -n<div class="im"><br>Kernel IP routing table<br>Destination Gateway Genmask Flags Metric Ref Use Iface<br></div>0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0<div class="im">
<br>
192.168.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0<br></div>root@vm:/var/lib/dhcp# ls<br>dhclient-7d27ffd3-3b9c-4d92-b81d-7ef16c1a965c-eth0.lease dhclient.leases<br>root@vm:/var/lib/dhcp# rm *<br>
root@vm:/var/lib/dhcp# ifconfig eth0 down<br>
root@vm:/var/lib/dhcp# ifconfig eth0 up<br>root@vm:/var/lib/dhcp# route -n<div class="im"><br>Kernel IP routing table<br>Destination Gateway Genmask Flags Metric Ref Use Iface<br></div><div class="im">
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0<br>
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0<br>192.168.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0<br></div>root@vm:/var/lib/dhcp# ls<br>dhclient-7d27ffd3-3b9c-4d92-b81d-7ef16c1a965c-eth0.lease<br>
root@vm:/var/lib/dhcp# cat dhclient-7d27ffd3-3b9c-4d92-b81d-7ef16c1a965c-eth0.lease<br>lease {<br> interface "eth0";<br> fixed-address 192.168.2.4;<br> option subnet-mask 255.255.255.0;<br> option routers 192.168.2.1;<br>
option dhcp-lease-time 120;<br> option dhcp-message-type 5;<br> option domain-name-servers 10.5.3.52;<br> option dhcp-server-identifier 192.168.2.2;<br> option dhcp-renewal-time 60;<br> option broadcast-address 192.168.2.255;<br>
option dhcp-rebinding-time 105;<br> option host-name "192-168-2-4";<br> option domain-name "openstacklocal";<br> renew 4 2013/04/25 07:06:57;<br> rebind 4 2013/04/25 07:07:47;<br> expire 4 2013/04/25 07:08:02;<br>
}<br>root@vm:/var/lib/dhcp#<br><br>root@vm:~#<br><br></div><div>Regards,<br>Balu<br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 25, 2013 at 12:07 PM, Leen Besselink <span dir="ltr"><<a href="mailto:ubuntu@consolejunkie.net" target="_blank">ubuntu@consolejunkie.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Balu ?<br>
<br>
Have you tried looking in the /var/lib/dhcp directory (the directory might depend<br>
on the DHCP-client you are using) of the Ubuntu image ?<br>
<br>
As this isn't a clean image but it has been connected to an other network, maybe a<br>
previous DHCP-server told it to add the route ? And now the client is just re-using<br>
an old lease ?<br>
<br>
On Wed, Apr 24, 2013 at 10:13:52PM -0700, Aaron Rosen wrote:<br>
> I'm not sure but if it works fine with the ubuntu cloud image and not with<br>
> your ubuntu image than there is something in your image adding that route.<br>
><br>
><br>
> On Wed, Apr 24, 2013 at 10:06 PM, Balamurugan V G<br>
> <<a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a>>wrote:<br>
><br>
> > Hi Aaron,<br>
> ><br>
> > I tried the image you pointed and it worked fine out of the box. That is<br>
> > it did not get the route to 169.254.0.0.26 on boot and I am able to<br>
> > retrieve info from metadata service. The image I was using earlier is a<br>
> > Ubuntu 12.04 LTS desktop image. What do you think could be wrong with my<br>
> > image? Its almost the vanilla Ubuntu image, I have not installed much. on<br>
> > it.<br>
> ><br>
> > Here is the quantum details you asked and more. This was taken before I<br>
> > tried the image you pointed to. And by the way, I have not added any host<br>
> > route as well.<br>
> ><br>
> > root@openstack-dev:~# quantum router-list<br>
> ><br>
> > +--------------------------------------+---------+--------------------------------------------------------+<br>
> > | id | name | external_gateway_info<br>
> > |<br>
> ><br>
> > +--------------------------------------+---------+--------------------------------------------------------+<br>
> > | d9e87e85-8410-4398-9ddd-2dbc36f4b593 | router1 | {"network_id":<br>
> > "e8862e1c-0233-481f-b284-b027039feef7"} |<br>
> ><br>
> > +--------------------------------------+---------+--------------------------------------------------------+<br>
> > root@openstack-dev:~# quantum net-list<br>
> ><br>
> > +--------------------------------------+---------+-----------------------------------------------------+<br>
> > | id | name | subnets<br>
> > |<br>
> ><br>
> > +--------------------------------------+---------+-----------------------------------------------------+<br>
> > | c4a7475e-e33f-47d0-a6ff-d0cf50c012d7 | net1 |<br>
> > ecdfe002-658e-4174-a33c-934ba09179b7 <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a> |<br>
> > | e8862e1c-0233-481f-b284-b027039feef7 | ext_net |<br>
> > 783e6a47-d7e0-46ba-9c2a-55a92406b23b <a href="http://10.5.12.20/24" target="_blank">10.5.12.20/24</a> |<br>
> ><br>
> > +--------------------------------------+---------+-----------------------------------------------------+<br>
> > *root@openstack-dev:~# quantum subnet-list<br>
> ><br>
> > +--------------------------------------+------+----------------+--------------------------------------------------+<br>
> > | id | name | cidr |<br>
> > allocation_pools |<br>
> ><br>
> > +--------------------------------------+------+----------------+--------------------------------------------------+<br>
> > | 783e6a47-d7e0-46ba-9c2a-55a92406b23b | | <a href="http://10.5.12.20/24" target="_blank">10.5.12.20/24</a> |<br>
> > {"start": "10.5.12.21", "end": "10.5.12.25"} |<br>
> > | ecdfe002-658e-4174-a33c-934ba09179b7 | | <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a> |<br>
> > {"start": "192.168.2.2", "end": "192.168.2.254"} |*<br>
> ><br>
> > +--------------------------------------+------+----------------+--------------------------------------------------+<br>
> > root@openstack-dev:~# quantum port-list<br>
> ><br>
> > +--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+<br>
> > | id | name | mac_address |<br>
> > fixed_ips<br>
> > |<br>
> ><br>
> > +--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+<br>
> > | 193bb8ee-f50d-4b1f-87ae-e033c1730953 | | fa:16:3e:91:3d:c0 |<br>
> > {"subnet_id": "783e6a47-d7e0-46ba-9c2a-55a92406b23b", "ip_address":<br>
> > "10.5.12.21"} |<br>
> > | 19bce882-c746-497b-b401-dedf5ab605b2 | | fa:16:3e:97:89:f6 |<br>
> > {"subnet_id": "783e6a47-d7e0-46ba-9c2a-55a92406b23b", "ip_address":<br>
> > "10.5.12.23"} |<br>
> > | 41ab9b15-ddc9-4a00-9a34-2e3f14e7e92f | | fa:16:3e:45:58:03 |<br>
> > {"subnet_id": "ecdfe002-658e-4174-a33c-934ba09179b7", "ip_address":<br>
> > "192.168.2.2"} |<br>
> > | 4dbc3c55-5763-4cfa-a7c1-81b254693e87 | | fa:16:3e:83:a7:e4 |<br>
> > {"subnet_id": "ecdfe002-658e-4174-a33c-934ba09179b7", "ip_address":<br>
> > "192.168.2.3"} |<br>
> > | 59e69986-6e8a-4f1e-a754-a1d421cdebde | | fa:16:3e:91:ee:76 |<br>
> > {"subnet_id": "ecdfe002-658e-4174-a33c-934ba09179b7", "ip_address":<br>
> > "192.168.2.1"} |<br>
> > | 65167653-f6ff-438b-b465-f5dcc8974549 | | fa:16:3e:a7:77:0b |<br>
> > {"subnet_id": "783e6a47-d7e0-46ba-9c2a-55a92406b23b", "ip_address":<br>
> > "10.5.12.24"} |<br>
> ><br>
> > +--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+<br>
> > root@openstack-dev:~# quantum floatingip-list<br>
> ><br>
> > +--------------------------------------+------------------+---------------------+--------------------------------------+<br>
> > | id | fixed_ip_address |<br>
> > floating_ip_address | port_id |<br>
> ><br>
> > +--------------------------------------+------------------+---------------------+--------------------------------------+<br>
> > | 1a5dfbf3-0986-461d-854e-f4f8ebb58f8d | 192.168.2.3 | 10.5.12.23<br>
> > | 4dbc3c55-5763-4cfa-a7c1-81b254693e87 |<br>
> > | f9d6e7f4-b251-4a2d-9310-532d8ee376f6 | | 10.5.12.24<br>
> > | |<br>
> ><br>
> > +--------------------------------------+------------------+---------------------+--------------------------------------+<br>
> > root@openstack-dev:~# quantum subnet-show<br>
> > ecdfe002-658e-4174-a33c-934ba09179b7<br>
> > +------------------+--------------------------------------------------+<br>
> > | Field | Value |<br>
> > +------------------+--------------------------------------------------+<br>
> > | allocation_pools | {"start": "192.168.2.2", "end": "192.168.2.254"} |<br>
> > | cidr | <a href="http://192.168.2.0/24" target="_blank">192.168.2.0/24</a> |<br>
> > | dns_nameservers | 10.5.3.52 |<br>
> > | enable_dhcp | True |<br>
> > | gateway_ip | 192.168.2.1 |<br>
> > | host_routes | |<br>
> > | id | ecdfe002-658e-4174-a33c-934ba09179b7 |<br>
> > | ip_version | 4 |<br>
> > | name | |<br>
> > | network_id | c4a7475e-e33f-47d0-a6ff-d0cf50c012d7 |<br>
> > | tenant_id | 7a416e3eaa814734bda41ffca7c2d01e |<br>
> > +------------------+--------------------------------------------------+<br>
> > root@openstack-dev:~# nova list<br>
> ><br>
> > +--------------------------------------+------+--------+------------------------------+<br>
> > | ID | Name | Status | Networks<br>
> > |<br>
> ><br>
> > +--------------------------------------+------+--------+------------------------------+<br>
> > | 99d57290-0d41-4478-8fb1-c9f9710a4b5b | VM1 | ACTIVE | net1=192.168.2.3,<br>
> > 10.5.12.23 |<br>
> ><br>
> > +--------------------------------------+------+--------+------------------------------+<br>
> > root@openstack-dev:~# nova show 99d57290-0d41-4478-8fb1-c9f9710a4b5b<br>
> ><br>
> > +-------------------------------------+--------------------------------------------------------------+<br>
> > | Property | Value<br>
> > |<br>
> ><br>
> > +-------------------------------------+--------------------------------------------------------------+<br>
> > | status | ACTIVE<br>
> > |<br>
> > | updated | 2013-04-25T04:22:39Z<br>
> > |<br>
> > | OS-EXT-STS:task_state | None<br>
> > |<br>
> > | OS-EXT-SRV-ATTR:host | openstack-dev<br>
> > |<br>
> > | key_name | None<br>
> > |<br>
> > | image | UbuntuDesktop1204_x86<br>
> > (943e86c3-5c92-48b7-8961-05f22bfb17d4) |<br>
> > | hostId |<br>
> > 6f4dd2cb679237445ddd8012fa1b0068fa9cb4881546fc5b15a6d296 |<br>
> > | OS-EXT-STS:vm_state | active<br>
> > |<br>
> > | OS-EXT-SRV-ATTR:instance_name | instance-00000021<br>
> > |<br>
> > | OS-EXT-SRV-ATTR:hypervisor_hostname |<br>
> > <a href="http://openstack-dev.blr.eng.sonicwall.com" target="_blank">openstack-dev.blr.eng.sonicwall.com</a> |<br>
> > | flavor | m1.tiny<br>
> > (1a2101c2-f20b-426d-b794-94d6a9418dfc) |<br>
> > | id |<br>
> > 99d57290-0d41-4478-8fb1-c9f9710a4b5b |<br>
> > | security_groups | [{u'name': u'default'}]<br>
> > |<br>
> > | user_id | 117e0142ab40418eafc56955f0ab2ba3<br>
> > |<br>
> > | name | VM1<br>
> > |<br>
> > | created | 2013-04-25T04:22:28Z<br>
> > |<br>
> > | tenant_id | 7a416e3eaa814734bda41ffca7c2d01e<br>
> > |<br>
> > | OS-DCF:diskConfig | MANUAL<br>
> > |<br>
> > | metadata | {}<br>
> > |<br>
> > | accessIPv4 |<br>
> > |<br>
> > | accessIPv6 |<br>
> > |<br>
> > | net1 network | 192.168.2.3, 10.5.12.23<br>
> > |<br>
> > | progress | 0<br>
> > |<br>
> > | OS-EXT-STS:power_state | 1<br>
> > |<br>
> > | OS-EXT-AZ:availability_zone | nova<br>
> > |<br>
> > | config_drive |<br>
> > |<br>
> ><br>
> > +-------------------------------------+--------------------------------------------------------------+<br>
> > root@openstack-dev:~# ip netns<br>
> > qdhcp-c4a7475e-e33f-47d0-a6ff-d0cf50c012d7<br>
> > qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593<br>
> ><br>
> > root@openstack-dev:~# ip netns exec<br>
> > qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n<br>
> > Kernel IP routing table<br>
> > Destination Gateway Genmask Flags Metric Ref Use<br>
> > Iface<br>
> > 0.0.0.0 10.5.12.1 0.0.0.0 UG 0 0 0<br>
> > qg-193bb8ee-f5<br>
> > 10.5.12.0 0.0.0.0 255.255.255.0 U 0 0 0<br>
> > qg-193bb8ee-f5<br>
> > 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0<br>
> > qr-59e69986-6e<br>
> > root@openstack-dev:~# ip netns exec<br>
> > qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 ifconfig<br>
> > lo Link encap:Local Loopback<br>
> > inet addr:127.0.0.1 Mask:255.0.0.0<br>
> > inet6 addr: ::1/128 Scope:Host<br>
> > UP LOOPBACK RUNNING MTU:16436 Metric:1<br>
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br>
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br>
> > collisions:0 txqueuelen:0<br>
> > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)<br>
> ><br>
> > qg-193bb8ee-f5 Link encap:Ethernet HWaddr fa:16:3e:91:3d:c0<br>
> > inet addr:10.5.12.21 Bcast:10.5.12.255 Mask:255.255.255.0<br>
> > inet6 addr: fe80::f816:3eff:fe91:3dc0/64 Scope:Link<br>
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
> > RX packets:121097 errors:0 dropped:104 overruns:0 frame:0<br>
> > TX packets:38777 errors:0 dropped:0 overruns:0 carrier:0<br>
> > collisions:0 txqueuelen:0<br>
> > RX bytes:88797723 (88.7 MB) TX bytes:3112197 (3.1 MB)<br>
> ><br>
> > qr-59e69986-6e Link encap:Ethernet HWaddr fa:16:3e:91:ee:76<br>
> > inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0<br>
> > inet6 addr: fe80::f816:3eff:fe91:ee76/64 Scope:Link<br>
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
> > RX packets:101615 errors:0 dropped:0 overruns:0 frame:0<br>
> > TX packets:68028 errors:0 dropped:0 overruns:0 carrier:0<br>
> > collisions:0 txqueuelen:0<br>
> > RX bytes:12476279 (12.4 MB) TX bytes:83025755 (83.0 MB)<br>
> ><br>
> > root@openstack-dev:~#<br>
> ><br>
> > Regards,<br>
> > Balu<br>
> ><br>
> ><br>
> ><br>
> > On Wed, Apr 24, 2013 at 11:32 PM, Aaron Rosen <<a href="mailto:arosen@nicira.com" target="_blank">arosen@nicira.com</a>> wrote:<br>
> ><br>
> >> Can you show us a quantum subnet-show for the subnet your vm has an ip<br>
> >> on. Is it possible that you added a host_route to the subnet for<br>
> >> 169.254/16?<br>
> >><br>
> >> Or could you try this image:<br>
> >> <a href="http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img" target="_blank">http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img</a><br>
> >><br>
> >><br>
> >> On Wed, Apr 24, 2013 at 1:06 AM, Balamurugan V G <<a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a><br>
> >> > wrote:<br>
> >><br>
> >>> I booted a Ubuntu Image in which I had made sure that there was no<br>
> >>> pre-existing route for 169,254.0.0/16. But its getting the route from DHCP<br>
> >>> once its boots up. So its the DHCP server which is sending this route to<br>
> >>> the VM.<br>
> >>><br>
> >>> Regards,<br>
> >>> Balu<br>
> >>><br>
> >>><br>
> >>> On Wed, Apr 24, 2013 at 12:47 PM, Balamurugan V G <<br>
> >>> <a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a>> wrote:<br>
> >>><br>
> >>>> Hi Salvatore,<br>
> >>>><br>
> >>>> Thanks for the response. I do not have enable_isolated_metadata_proxy<br>
> >>>> anywhere under /etc/quantum and /etc/nova. The closest I see is<br>
> >>>> 'enable_isolated_metadata' in /etc/quantum/dhcp_agent.ini and even that is<br>
> >>>> commented out. What do you mean by link-local address?<br>
> >>>><br>
> >>>> Like you said, I suspect that the image has the route. This was was a<br>
> >>>> snapshot taken in a Folsom setup. So its possible that Folsom has injected<br>
> >>>> this route and when I took the snapshot, it became part of the snapshot. I<br>
> >>>> then copied over this snapshot to a new Grizzly setup. Let me check the<br>
> >>>> image and remove it from the image if it has the route. Thanks for the hint<br>
> >>>> again.<br>
> >>>><br>
> >>>> Regards,<br>
> >>>> Balu<br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>> On Wed, Apr 24, 2013 at 12:38 PM, Salvatore Orlando <<br>
> >>>> <a href="mailto:sorlando@nicira.com" target="_blank">sorlando@nicira.com</a>> wrote:<br>
> >>>><br>
> >>>>> The dhcp agent will set a route to <a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> if<br>
> >>>>> enable_isolated_metadata_proxy=True.<br>
> >>>>> In that case the dhcp port ip will be the nexthop for that route.<br>
> >>>>><br>
> >>>>> Otherwise, it might be your image might have a 'builtin' route to such<br>
> >>>>> cidr.<br>
> >>>>> What's your nexthop for the link-local address?<br>
> >>>>><br>
> >>>>> Salvatore<br>
> >>>>><br>
> >>>>><br>
> >>>>> On 24 April 2013 08:00, Balamurugan V G <<a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a>>wrote:<br>
> >>>>><br>
> >>>>>> Thanks for the hint Aaron. When I deleted the route for<br>
> >>>>>> <a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> from the VMs routing table, I could access the<br>
> >>>>>> metadata service!<br>
> >>>>>><br>
> >>>>>> The route for <a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> is added automatically when the<br>
> >>>>>> instance boots up, so I assume its coming from the DHCP. Any idea how this<br>
> >>>>>> can be suppressed?<br>
> >>>>>><br>
> >>>>>> Strangely though, I do not see this route in a WindowsXP VM booted in<br>
> >>>>>> the same network as the earlier Ubuntu VM and the Windows VM can reach the<br>
> >>>>>> metadata service with out me doing anything. The issue is with the Ubuntu<br>
> >>>>>> VM.<br>
> >>>>>><br>
> >>>>>> Thanks,<br>
> >>>>>> Balu<br>
> >>>>>><br>
> >>>>>><br>
> >>>>>><br>
> >>>>>> On Wed, Apr 24, 2013 at 12:18 PM, Aaron Rosen <<a href="mailto:arosen@nicira.com" target="_blank">arosen@nicira.com</a>>wrote:<br>
> >>>>>><br>
> >>>>>>> The vm should not have a routing table entry for <a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> if<br>
> >>>>>>> it does i'm not sure how it got there unless it was added by something<br>
> >>>>>>> other than dhcp. It seems like that is your problem as the vm is arping<br>
> >>>>>>> directly for that address rather than the default gw.<br>
> >>>>>>><br>
> >>>>>>><br>
> >>>>>>> On Tue, Apr 23, 2013 at 11:34 PM, Balamurugan V G <<br>
> >>>>>>> <a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a>> wrote:<br>
> >>>>>>><br>
> >>>>>>>> Thanks Aaron.<br>
> >>>>>>>><br>
> >>>>>>>> I am perhaps not configuring it right then. I am using Ubuntu 12.04<br>
> >>>>>>>> host and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see<br>
> >>>>>>>> that the VM's routing table has an entry for <a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> but I<br>
> >>>>>>>> cant ping 169.254.169.254 from the VM. I am using a single node setup with<br>
> >>>>>>>> two NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP<br>
> >>>>>>>><br>
> >>>>>>>> These are my metadata related configurations.<br>
> >>>>>>>><br>
> >>>>>>>> */etc/nova/nova.conf *<br>
> >>>>>>>> metadata_host = 10.5.12.20<br>
> >>>>>>>> metadata_listen = 127.0.0.1<br>
> >>>>>>>> metadata_listen_port = 8775<br>
> >>>>>>>> metadata_manager=nova.api.manager.MetadataManager<br>
> >>>>>>>> service_quantum_metadata_proxy = true<br>
> >>>>>>>> quantum_metadata_proxy_shared_secret = metasecret123<br>
> >>>>>>>><br>
> >>>>>>>> */etc/quantum/quantum.conf*<br>
> >>>>>>>> allow_overlapping_ips = True<br>
> >>>>>>>><br>
> >>>>>>>> */etc/quantum/l3_agent.ini*<br>
> >>>>>>>> use_namespaces = True<br>
> >>>>>>>> auth_url = <a href="http://10.5.3.230:35357/v2.0" target="_blank">http://10.5.3.230:35357/v2.0</a><br>
> >>>>>>>> auth_region = RegionOne<br>
> >>>>>>>> admin_tenant_name = service<br>
> >>>>>>>> admin_user = quantum<br>
> >>>>>>>> admin_password = service_pass<br>
> >>>>>>>> metadata_ip = 10.5.12.20<br>
> >>>>>>>><br>
> >>>>>>>> */etc/quantum/metadata_agent.ini*<br>
> >>>>>>>> auth_url = <a href="http://10.5.3.230:35357/v2.0" target="_blank">http://10.5.3.230:35357/v2.0</a><br>
> >>>>>>>> auth_region = RegionOne<br>
> >>>>>>>> admin_tenant_name = service<br>
> >>>>>>>> admin_user = quantum<br>
> >>>>>>>> admin_password = service_pass<br>
> >>>>>>>> nova_metadata_ip = 127.0.0.1<br>
> >>>>>>>> nova_metadata_port = 8775<br>
> >>>>>>>> metadata_proxy_shared_secret = metasecret123<br>
> >>>>>>>><br>
> >>>>>>>><br>
> >>>>>>>> I see that /usr/bin/quantum-ns-metadata-proxy process is running.<br>
> >>>>>>>> When I ping 169.254.169.254 from VM, in the host's router namespace, I see<br>
> >>>>>>>> the ARP request but no response.<br>
> >>>>>>>><br>
> >>>>>>>> root@openstack-dev:~# ip netns exec<br>
> >>>>>>>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n<br>
> >>>>>>>> Kernel IP routing table<br>
> >>>>>>>> Destination Gateway Genmask Flags Metric Ref<br>
> >>>>>>>> Use Iface<br>
> >>>>>>>> 0.0.0.0 10.5.12.1 0.0.0.0 UG 0<br>
> >>>>>>>> 0 0 qg-193bb8ee-f5<br>
> >>>>>>>> 10.5.12.0 0.0.0.0 255.255.255.0 U 0<br>
> >>>>>>>> 0 0 qg-193bb8ee-f5<br>
> >>>>>>>> 192.168.2.0 0.0.0.0 255.255.255.0 U 0<br>
> >>>>>>>> 0 0 qr-59e69986-6e<br>
> >>>>>>>> root@openstack-dev:~# ip netns exec<br>
> >>>>>>>> qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 tcpdump -i qr-59e69986-6e<br>
> >>>>>>>> tcpdump: verbose output suppressed, use -v or -vv for full protocol<br>
> >>>>>>>> decode<br>
> >>>>>>>> listening on qr-59e69986-6e, link-type EN10MB (Ethernet), capture<br>
> >>>>>>>> size 65535 bytes<br>
> >>>>>>>> ^C23:32:09.638289 ARP, Request who-has 192.168.2.3 tell<br>
> >>>>>>>> 192.168.2.1, length 28<br>
> >>>>>>>> 23:32:09.650043 ARP, Reply 192.168.2.3 is-at fa:16:3e:4f:ad:df (oui<br>
> >>>>>>>> Unknown), length 28<br>
> >>>>>>>> 23:32:15.768942 ARP, Request who-has 169.254.169.254 tell<br>
> >>>>>>>> 192.168.2.3, length 28<br>
> >>>>>>>> 23:32:16.766896 ARP, Request who-has 169.254.169.254 tell<br>
> >>>>>>>> 192.168.2.3, length 28<br>
> >>>>>>>> 23:32:17.766712 ARP, Request who-has 169.254.169.254 tell<br>
> >>>>>>>> 192.168.2.3, length 28<br>
> >>>>>>>> 23:32:18.784195 ARP, Request who-has 169.254.169.254 tell<br>
> >>>>>>>> 192.168.2.3, length 28<br>
> >>>>>>>><br>
> >>>>>>>> 6 packets captured<br>
> >>>>>>>> 6 packets received by filter<br>
> >>>>>>>> 0 packets dropped by kernel<br>
> >>>>>>>> root@openstack-dev:~#<br>
> >>>>>>>><br>
> >>>>>>>><br>
> >>>>>>>> Any help will be greatly appreciated.<br>
> >>>>>>>><br>
> >>>>>>>> Thanks,<br>
> >>>>>>>> Balu<br>
> >>>>>>>><br>
> >>>>>>>><br>
> >>>>>>>> On Wed, Apr 24, 2013 at 11:48 AM, Aaron Rosen <<a href="mailto:arosen@nicira.com" target="_blank">arosen@nicira.com</a>>wrote:<br>
> >>>>>>>><br>
> >>>>>>>>> Yup, If your host supports namespaces this can be done via the<br>
> >>>>>>>>> quantum-metadata-agent. The following setting is also required in your<br>
> >>>>>>>>> nova.conf: service_quantum_metadata_proxy=True<br>
> >>>>>>>>><br>
> >>>>>>>>><br>
> >>>>>>>>> On Tue, Apr 23, 2013 at 10:44 PM, Balamurugan V G <<br>
> >>>>>>>>> <a href="mailto:balamuruganvg@gmail.com" target="_blank">balamuruganvg@gmail.com</a>> wrote:<br>
> >>>>>>>>><br>
> >>>>>>>>>> Hi,<br>
> >>>>>>>>>><br>
> >>>>>>>>>> In Grizzly, when using quantum and overlapping IPs, does metadata<br>
> >>>>>>>>>> service work? This wasnt working in Folsom.<br>
> >>>>>>>>>><br>
> >>>>>>>>>> Thanks,<br>
> >>>>>>>>>> Balu<br>
> >>>>>>>>>><br>
> >>>>>>>>>> _______________________________________________<br>
> >>>>>>>>>> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> >>>>>>>>>> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> >>>>>>>>>> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> >>>>>>>>>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> >>>>>>>>>><br>
> >>>>>>>>>><br>
> >>>>>>>>><br>
> >>>>>>>><br>
> >>>>>>><br>
> >>>>>><br>
> >>>>>> _______________________________________________<br>
> >>>>>> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> >>>>>> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> >>>>>> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> >>>>>> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> >>>>>><br>
> >>>>>><br>
> >>>>><br>
> >>>><br>
> >>><br>
> >><br>
> ><br>
<br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>