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

OpenStack Swift - Container Sync (New & Old ways)

Image
OpenStack Swift Container-Sync  Swift 內建功能利用背景工作, 讓 Container to Container 如同鏡像一樣同步所有資料. 不僅僅是自己的Container, 還可以跟其他人Account內的Container相互同步資料. 這個功能也被部分企業用來將資料從舊的Swift Cluster轉移到新的環境上. 提示 如果User request是對object做POST的操作, 操作內容不一定會被同步, 除非object_post_as_copy = true 在 Proxy server 的設定, 目前這個值預設為開啟 true. 同步的設定可以有幾種模式 : One-way sync : 單向同步 containerA --> containerB Two-way sync : 雙向同步 containerA <--> containerB Chain : 鏈狀同步 containerA --> containerB --> containerC --> containerA 首先你必須要知道目前有兩種方法(新/舊)來設定 Container Sync First of all, you need to know there are two styles for setting container-sync currently.  OLD-style(舊): Supported since Swift's initial release. 任何版本,包含新版本 NEW-style(新): Implemented in Swift 1.12  or later. 在1.12版本後才釋出 不論新舊styles, 都有一個重要的前提, 原資料所在的Container Server, 必須要能跟遠端目標Container 的 Proxy Server 透過網路連結的到. NEW-Style - 多了realm(域)的觀念. 新的做法需要先建立一個設定檔 ( /etc/swift/container-sync-realms.conf )在兩個叢集的"所有"節點. 具體一點來說, 只要會涉及到這個同步過程的所有Pro
Read more