[Openstack-operators] 169.254.269.254 is driven me insane
leandro.reox at gmail.com
Fri May 27 21:05:04 UTC 2011
Sorry for the typo the ip add is 169.254.169.254 :)
On Fri, May 27, 2011 at 5:01 PM, Leandro Reox <leandro.reox at gmail.com>wrote:
> Hi all,
> In a multinode environment has anyone succeed booting up images ( ubuntu -
> cloud init ) that request the metadata to the ip 169.254.269.254 ?
> NOTE: instances booting on the controller node (that has also compute
> services running, boots up ok ... no luck getting instances running on the
> ADDITIONAL compute node :( )
> - Already tried
> -- iptables rule on the controller/network node
> -- ip addres on the loopback controller/network node
> -- ip address on the br100 controller/network node
> -- static route on the aditional compute node
> -- iptables rule on the aditional compute node
> -- ip address on the loopback on the aditional compute node
> -- ip address on the br100 on the aditional compute node
> Still the same ugly message !
> tcpdumping all over the network , the request is sent back from the network
> node repliing with the 169.254.269.254 but doesnt getting into the VM ?
> Any clues of how to get this working ????
> Best Regards
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack-operators