Comment 6 for bug 719798
Revision history for this message
| Vish Ishaya (vishvananda) wrote Re: Instance fails to access metadata server | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
If this is a desktop image, you may have to give the 169.254 address to the network host:
something like:
ip addr add 169.254.169.254/32 scope link dev eth1
This will allow it to arp for the address. The eth device that you add the address to isn't particularly important, although if you decide to add it to br100 you should probably use scope global instead of scope link, or the ordering of ip addresses can sometimes mess up dhcp.
If this is not a desktop image, then you may be having issues with your forwarding rules. Check:
iptables -L -n -v
for the 169.254 rule. Make sure that the rule has the proper ip for your api server and make sure that the rule is actually getting hit properly.
The ip addr add command really needs to be done automatically. I consider this a must have for cactus. The workaround of adding it manually is too much to expect users to have to do