DHCP namespace doesn't have IPv6 default route
Bug #1684682 reported by
Dr. Jens Harbott
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.
Changed in neutron: | |
importance: | Medium → High |
To post a comment you must log in.
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.