Could you please issue 'route -n' on your VM and check if 169.254.0.0/16 does have its own route ? If yes, delete it. Another classic error is to forget to add a static route from the controller node (if hosting metadata service) to the external router IP of the VM (see http://docs.openstack.org/folsom/openstack-network/admin/content/adv_cfg_l3_agent_metadata.html ) -Sylvain Le 04/03/2013 15:29, livemoon a écrit : > Hi, I am follow > http://docs.openstack.org/folsom/basic-install/content/ and set up > three nodes folsom. > Now I have found my vm cannot get 169.254.169.254 to get cloud-init > data. So I check the network node(quantum), using "iptables -L -t > nat", I have found: > > *Chain quantum-l3-agent-PREROUTING (1 references)* > *target prot opt source destination* > *DNAT tcp -- anywhere 169.254.169.254 tcp > dpt:http to:192.168.1.2:8775* > > I think it is correct, and in the network node, I can ping and curl > "192.168.1.2"(this is controller node"), but not ping and curl > 169.254.169.254. > > Can anyone help me? > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130304/3571e62b/attachment.html>