Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

The problem is, that 169.254.169.254 [metadata server virtual ip] is not accessible from the physical router on the network. That metadata server lives in a netnamespace on the network node - not on the physical router. This has been thought through in Icehouse, and the traffic to 169.254.169.254 can now be routed trough the DHCP server.

Here is my sollution: 1. Edit /etc/neutron/dhcp-agent.ini with:

enable_isolated_metadata = True

  1. Stop all agents and neutron-server on the network node

  2. $ sudo killall dnsmasq

  3. Start all the agents on the network node

  4. Enjoy your network with metadata server. In my case the routing table of the instance looks like this:

    $ route -n

    Kernel IP routing table

    Destination Gateway Genmask Flags Metric Ref Use Iface

    0.0.0.0 31.13.250.1 0.0.0.0 UG 0 0 0 eth0

    31.13.250.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0

    169.254.169.254 31.13.250.12 255.255.255.255 UGH 0 0 0 eth0

  5. If you are using cirros, please update to latest release.

More info: https://ask.openstack.org/en/question/27505/metadata-problem-in-neutron-flat-network/