openstack team mailing list archive

[Dan Wendlandt <dan@xxxxxxxxxx>]

On Mon, Mar 4, 2013 at 6:44 AM, Sylvain Bauza <sylvain.bauza@xxxxxxxxxxxx>wrote:

>  Could you please issue 'route -n' on your VM and check if 169.254.0.0/16does 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)
>
>
The good news is that this will no longer be a requirement in Grizzly,
thanks to Mark's work on integrating metadata into Quantum.  Thanks Mark!

Dan



> -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@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~