yahoo-eng-team team mailing list archive

[OpenStack Infra <1684682@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/461887
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ad7584ce113bff21999d6ffd155334bf3d05d2f
Submitter: Jenkins
Branch:    master

commit 7ad7584ce113bff21999d6ffd155334bf3d05d2f
Author: Brian Haley <bhaley@xxxxxxxxxx>
Date:   Tue May 2 15:25:17 2017 -0400

    Add IPv6 default route to DHCP namespace
    
    The DHCP namespace used to always have its IPv6 default
    route configured from a received Router Advertisement (RA).
    A recent change [1] disabled receipt of RAs, instead
    relying on the network topology to configure the namespace.
    Unfortunately the code only added an IPv4 default route,
    which caused a regression with DNS resolution in some
    circumstances where IPv6 was being used.
    
    A default route is now added for both IP versions.
    
    [1] https://review.openstack.org/#/c/386687/
    
    Change-Id: I7c388f64c0aa9feb002f7a2faf76e7ccca30a3e7
    Closes-bug: 1684682


** 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/1684682

Title:
  DHCP namespace doesn't have IPv6 default route

Status in neutron:
  Fix Released

Bug description:
  This is a regression for Ocata, things are working fine for Newton.
  But if I create a IPv6 subnet in Ocata, the DHCP namespace gets
  configured with an IPv6 address, but is lacking a default route, so
  dnsmasq fails to resolv any DNS queries except for the local OpenStack
  instances.

  I think there have been some changes in the way the namespace is being
  set up, removing listening to RAs and instead doing static
  configuration, that may have caused this.

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