yahoo-eng-team team mailing list archive

[OpenStack Infra <1556991@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/293237
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=784864d1785bcd32297865cae5a7a243b05ed30d
Submitter: Jenkins
Branch:    master

commit 784864d1785bcd32297865cae5a7a243b05ed30d
Author: Hong Hui Xiao <xiaohhui@xxxxxxxxxx>
Date:   Mon Mar 14 13:19:52 2016 +0000

    Update metadata proxy when subnet add/delete
    
    With current code, if first subnet of the network is an ipv6 subnet,
    the metadata proxy will not be spawned. If user then adds ipv4 subnet
    with dhcp enabled, the metadata proxy will still not be spawned. As a
    result, the metadata service will not be available for the network.
    
    This patch will kill/spawn metadata proxy,  when subnet add/delete.
    So, even if the first subnet of the network is not an ipv4 subnet with
    dhcp enabled, the metadata proxy can still be spawned if network has
    subnets need metadata proxy.
    
    Closes-bug: #1556991
    
    Change-Id: I0b45af8f2b756732f45c13d7e2dbcd30653cc026


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  Isolated metadata will not work if ipv6 subnet is created first

Status in neutron:
  Fix Released

Bug description:
  IPv6 metadata is not supported yet. The discussion is at [1].

  I want to use IPv4 isolated metadata service. And found this issue,

  1) Set "enable_isolated_metadata = True" in configuration.
  2) Create a network.
  3) Create a Ipv6 subnet for it. According to [2], the metadata proxy will not be created
  4) Create a ipv4 subnet for the network.
  5) Boot a vm in the network.
  6) The VM can't use metadata service. curl 169.254.169.254 will report "curl: (7) couldn't connect to host". The route to the dhcp port has been in the VM,

  $ ip r
  default via 30.0.0.1 dev eth0 
  30.0.0.0/24 dev eth0  src 30.0.0.3 
  169.254.169.254 via 30.0.0.2 dev eth0 

  But the process of metadata proxy can not be found in the OS.

  
  Expected: the VM can use metadata service.

  [1] https://bugs.launchpad.net/neutron/+bug/1460177
  [2] https://github.com/openstack/neutron/blob/53c03f5ed32d043cf963c6b67e4afa6d42ef1eaa/neutron/agent/dhcp/agent.py#L246-L249

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