Comment 3 for bug 719798
Revision history for this message
| Wayne A. Walls (wayne-walls) wrote Re: Instance fails to access metadata server | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Greetings!
I've messed around quite a bit with the UEC images, and I found if you add an iptables NAT wherever your nova-api services runs it fixes the boot problems. You would want something like this...
iptables -t nat -A PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination <NOVA-API-
Thierry is right though, VlanManager /usually/ doesn't need this, but it's worth a shot. Lastly, to be honest, it looks like there is more going on with your UEC image than just the metadata server not getting contacted...if that was the only case, you'd likely see something more along, 'Cannot reach metadata server ... trying again 1/100.' The image will try 100 times to contact the metadata server, and if it can't it will sometimes continue booting, but in my experience it just loops :(
Give it a try, and let us know how it goes!
Cheers