Failed to get metadata from 169.254.169.254


Comments

  1. GrahamHJune 17, 2011 at 5:24 AM

    Hugo, I am running into metadata failure also with a very similar setup. How did you resolve this issue?

    Thanks,
    Graham

    ReplyDelete
  2. Hugo KuoJune 17, 2011 at 10:13 AM

    Could you show me your entire topology for me ?
    and console output for me ....
    the clue is in console output
    something like
    And the debug skill is , connect my laptop to same network with instance. Then "#curl 169.254.169.254" from your laptop.

    The reason of failed might difference. The most issue is instance network can not redirect 169.254.169.254 request to nova-api.

    If you use only one nic for nova-network , you can try to turn on PROMISC mode of the interface.
    "#ip link set dev br100 promisc on"

    Remember the point of this issue is "instance request could not redirect to nova-api server"

    ReplyDelete
  3. rohitDecember 19, 2018 at 5:04 PM


    Very Nice blog for learning new things,thanks for such beautiful blog.
    below some new idea plz check once.
    KissAnime

    ReplyDelete

Post a Comment

Popular posts from this blog

The method of Web Service HA+LB in OPENSTACK NOVA for private cloud only

Image
Cloud Server HA+LB  in NOVA Our purpose is to provide uninterrupted   web services  with low cost in OPENSTACK. Due to all instances traffic through Nova-Network host in a basic deployment of NOVA . And it's hard to do HA+LB for Nova-Network. As I know it will be very hard to implement.  After read "Bootstrapping OpenStack Clouds" doc writed by DELL....The fault zone concept it much easier and cheaper.  There're three diagrams .... I. Two zones topology , share nothing between each zones. But combine two instance network in same network segment. Zone1 using 192.168.1.0/25,   Zone2 using 192.168.1.128/25 . We do  not using floating ip.  Let instance route from Core Network  Switch directly.
Read more