Balu ?
Have you tried looking in the /var/lib/dhcp directory (the directory might
depend
on the DHCP-client you are using) of the Ubuntu image ?
As this isn't a clean image but it has been connected to an other network,
maybe a
previous DHCP-server told it to add the route ? And now the client
On Thu, Apr 25, 2013 at 12:45:03PM +0530, Balamurugan V G wrote:
Hi Leen,
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
Yup, If your host supports namespaces this can be done via the
quantum-metadata-agent. The following setting is also required in your
nova.conf: service_quantum_metadata_proxy=True
On Tue, Apr 23, 2013 at 10:44 PM, Balamurugan V G
balamuruga...@gmail.comwrote:
Hi,
In Grizzly, when using
Thanks Aaron.
I am perhaps not configuring it right then. I am using Ubuntu 12.04 host
and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see that
the VM's routing table has an entry for 169.254.0.0/16 but I cant ping
169.254.169.254 from the VM. I am using a single node setup with
The vm should not have a routing table entry for 169.254.0.0/16 if it does
i'm not sure how it got there unless it was added by something other than
dhcp. It seems like that is your problem as the vm is arping directly for
that address rather than the default gw.
On Tue, Apr 23, 2013 at 11:34
Thanks for the hint Aaron. When I deleted the route for 169.254.0.0/16 from
the VMs routing table, I could access the metadata service!
The route for 169.254.0.0/16 is added automatically when the instance boots
up, so I assume its coming from the DHCP. Any idea how this can be
suppressed?
Hrm, I'd do quantum subnet-list and see if you happened to create a subnet
169.254.0.0/16? Otherwise I think there is probably some software in your
vm image that is adding this route. One thing to test is if you delete this
route and then rerun dhclient to see if it's added again via dhcp.
On
The dhcp agent will set a route to 169.254.0.0/16 if
enable_isolated_metadata_proxy=True.
In that case the dhcp port ip will be the nexthop for that route.
Otherwise, it might be your image might have a 'builtin' route to such
cidr.
What's your nexthop for the link-local address?
Salvatore
On
Yup, That's only if your subnet does not have a default gateway set.
Providing the output of route -n would be helpful .
On Wed, Apr 24, 2013 at 12:08 AM, Salvatore Orlando sorla...@nicira.comwrote:
The dhcp agent will set a route to 169.254.0.0/16 if
enable_isolated_metadata_proxy=True.
In
Hi Salvatore,
Thanks for the response. I do not have enable_isolated_metadata_proxy
anywhere under /etc/quantum and /etc/nova. The closest I see is
'enable_isolated_metadata' in /etc/quantum/dhcp_agent.ini and even that is
commented out. What do you mean by link-local address?
Like you said, I
I do not have any thing running in the VM which could add this route. With
the route removed, when I disable and enable networking, so that it gets
back the details from DHCP server, I see that the route is getting added
again.
So DHCP seems to be my issue. I guess this rules out any pre-existing
The routing table in the VM is:
root@vm:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 192.168.2.1 0.0.0.0 UG0 00 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0
I booted a Ubuntu Image in which I had made sure that there was no
pre-existing route for 169,254.0.0/16. But its getting the route from DHCP
once its boots up. So its the DHCP server which is sending this route to
the VM.
Regards,
Balu
On Wed, Apr 24, 2013 at 12:47 PM, Balamurugan V G
Can you show us a quantum subnet-show for the subnet your vm has an ip on.
Is it possible that you added a host_route to the subnet for 169.254/16?
Or could you try this image:
http://cloud-images.ubuntu.com/precise/current/precise-server-cloudimg-amd64-disk1.img
On Wed, Apr 24, 2013 at 1:06
Hi Balu!
Listen, is your metadata service up and running?!
If yes, which guide you used?
I'm trying everything I can to enable metadata without L3 with a Quantum
Single Flat topology for my own guide:
https://gist.github.com/tmartinx/d36536b7b62a48f859c2
I really appreciate any feedback!
Tks!
Hi Aaron,
I tried the image you pointed and it worked fine out of the box. That is it
did not get the route to 169.254.0.0.26 on boot and I am able to retrieve
info from metadata service. The image I was using earlier is a Ubuntu 12.04
LTS desktop image. What do you think could be wrong with my
I'm not sure but if it works fine with the ubuntu cloud image and not with
your ubuntu image than there is something in your image adding that route.
On Wed, Apr 24, 2013 at 10:06 PM, Balamurugan V G
balamuruga...@gmail.comwrote:
Hi Aaron,
I tried the image you pointed and it worked fine out
17 matches
Mail list logo
