Hello, On my newly installed grizzly testbed, which has one controller, one network host (quantum/ovs) and one compute node, there is an issue with metadata service: From the instance, its routing table looks like this: [root@host-172-16-0-8 ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.0.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0 0.0.0.0 172.16.0.1 0.0.0.0 UG 0 0 0 eth0 And metadata service is not reachable, the curl command complains about "no route to 169.254.169.254". After deleting the 169.254.0.0/16 entry from the routing table, the metadata service works. Why would quantum append the 169.254.0.0 route into the routing table of the VM instance ? I have enable_isolated_metadata set to False in the dhcp_agent.ini. Thanks, Xin