← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1618013] Re: metadata route is absent and metadata server unavailable for instance with network w/o gateway

 

Old bug. I'm going to mark this as Invalid for neutron since there is a
flag to control the behavior, forcing the dhcp-agent to provide a route
if the network is isolated.

In the dhcp-agent.ini file you should un-comment and set this value to
True:

# The DHCP server can assist with providing metadata support on isolated
# networks. Setting this value to True will cause the DHCP server to append
# specific host routes to the DHCP request. The metadata service will only be
# activated when the subnet does not contain any router port. The guest
# instance must be configured to request host routes via DHCP (Option 121).
# This option doesn't have any effect when force_metadata is set to True.
# (boolean value)
enable_isolated_metadata = true

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1618013

Title:
  metadata route is absent and metadata server unavailable for instance
  with network w/o gateway

Status in neutron:
  Invalid
Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  ubuntu 14.04
  latest devstack (28.08.2016)
  enabled services: nova, glance, cinder, keystone, horizon, neutron, neutron-vpnaas, ec2-api

  steps to reproduce:
  0) source demo credentials
  1) create network
  2) create subnet without gateway
  3) boot instance from cirros image
  4) run vnc console
  5) run 'route -n':
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
  10.10.0.0       10.10.2.1       255.255.0.0     UG    0      0        0 eth0
  10.10.2.0       0.0.0.0         255.255.255.0   U     0      0        0 eth0

  6) run 'curl http://169.254.169.254/latest/'
  curl: (7) Failed to connect to 169.254.169.254: Network is unreachable

  
  if user runs instance with predefined network that all works well:
  $ route -n
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
  0.0.0.0         10.10.1.1       0.0.0.0         UG    0      0        0 eth0
  10.10.0.0       10.10.1.1       255.255.0.0     UG    0      0        0 eth0
  10.10.1.0       0.0.0.0         255.255.255.0   U     0      0        0 eth0
  169.254.169.254 10.10.1.1       255.255.255.255 UGH   0      0        0 eth0

  
  according to gating jobs it was broken between "Aug 25 2:05 PM" (last check pipeline - https://review.openstack.org/#/c/360230/)
  and "Aug 26 1:05 AM" (patch 4 first check pipeline - https://review.openstack.org/#/c/357766/)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1618013/+subscriptions



References