DHCP namespace doesn't have IPv6 default route

Bug #1684682 reported by Dr. Jens Harbott
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Brian Haley

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.

Revision history for this message
Brian Haley (brian-haley) wrote :

This is probably due to https://review.openstack.org/#/c/386687/ (Disable 'accept_ra' in DHCP agent namespace). The default route should have been added based on the network topology, but it looks like it's only done for IPv4 in _set_default_route() in the DHCP code.

I'll work on a fix.

Changed in neutron:
status: New → Confirmed
assignee: nobody → Brian Haley (brian-haley)
tags: added: ipv6 l3-ipam-dhcp
Changed in neutron:
importance: Undecided → Medium
Changed in neutron:
importance: Medium → High
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/461887

Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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 <email address hidden>
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/469301

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/469302

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 11.0.0.0b2

This issue was fixed in the openstack/neutron 11.0.0.0b2 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/newton)

Reviewed: https://review.openstack.org/469302
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=afdc38f7c68228a7aaa6e5f2eb0871073f306722
Submitter: Jenkins
Branch: stable/newton

commit afdc38f7c68228a7aaa6e5f2eb0871073f306722
Author: Brian Haley <email address hidden>
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
    (cherry picked from commit 7ad7584ce113bff21999d6ffd155334bf3d05d2f)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/ocata)

Reviewed: https://review.openstack.org/469301
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b124e6835edda28eb1548c0ed32e596dc1ed131f
Submitter: Jenkins
Branch: stable/ocata

commit b124e6835edda28eb1548c0ed32e596dc1ed131f
Author: Brian Haley <email address hidden>
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
    (cherry picked from commit 7ad7584ce113bff21999d6ffd155334bf3d05d2f)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 9.4.1

This issue was fixed in the openstack/neutron 9.4.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 10.0.3

This issue was fixed in the openstack/neutron 10.0.3 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.