yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #58486
[Bug 1640271] [NEW] Prefix delegation: bind LLA is removed from the gateway port with a regular neutron router
Public bug reported:
Following the wiki http://docs.openstack.org/mitaka/networking-guide
/config-ipv6.html, setup PD in a openstack deployment. Create a router
and add a PD-enabled subnet as in below:
neutron net-create ipv6-pd-net
neutron subnet-create --ip-version 6 --name ipv6-pd-subnet --ipv6-address-mode slaac --ipv6-ra-mode slaac --use-default-subnetpool ipv6-pd-net
neutron router-create pd-router
neutron router-interface-add pd-router ipv6-pd-subnet
neutron router-gateway-set pd-router public
Prefix will be obtained successfully. However, check the router
namespace, and the bind LLA for the dibbler client that is created to
request for prefix no longer exists any more. The only LLA shown is the
default LLA on the qg-xxx interface.
231: qg-302d8d0d-65: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether fa:16:3e:3a:92:b5 brd ff:ff:ff:ff:ff:ff
inet 172.24.4.10/24 brd 172.24.4.255 scope global qg-302d8d0d-65
valid_lft forever preferred_lft forever
inet6 2001:db8::a/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe3a:92b5/64 scope link
valid_lft forever preferred_lft forever
See logs in the attachment that shows the bind LLA is removed the second
time the gateway port is updated by init_router_port().
This means, the renewing of the prefix by the dibbler client will be
failing later.
https://bugs.launchpad.net/neutron/+bug/1639042 reported a symptom that
is also caused by the removal of the bind LLA. Both bugs may share the
same root cause: bind LLA should be preserved until the pd subnet is
removed from the router.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: ipv6
** Attachment added: "lla-q-l3.log"
https://bugs.launchpad.net/bugs/1640271/+attachment/4774505/+files/lla-q-l3.log
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1640271
Title:
Prefix delegation: bind LLA is removed from the gateway port with a
regular neutron router
Status in neutron:
New
Bug description:
Following the wiki http://docs.openstack.org/mitaka/networking-guide
/config-ipv6.html, setup PD in a openstack deployment. Create a router
and add a PD-enabled subnet as in below:
neutron net-create ipv6-pd-net
neutron subnet-create --ip-version 6 --name ipv6-pd-subnet --ipv6-address-mode slaac --ipv6-ra-mode slaac --use-default-subnetpool ipv6-pd-net
neutron router-create pd-router
neutron router-interface-add pd-router ipv6-pd-subnet
neutron router-gateway-set pd-router public
Prefix will be obtained successfully. However, check the router
namespace, and the bind LLA for the dibbler client that is created to
request for prefix no longer exists any more. The only LLA shown is
the default LLA on the qg-xxx interface.
231: qg-302d8d0d-65: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
link/ether fa:16:3e:3a:92:b5 brd ff:ff:ff:ff:ff:ff
inet 172.24.4.10/24 brd 172.24.4.255 scope global qg-302d8d0d-65
valid_lft forever preferred_lft forever
inet6 2001:db8::a/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe3a:92b5/64 scope link
valid_lft forever preferred_lft forever
See logs in the attachment that shows the bind LLA is removed the
second time the gateway port is updated by init_router_port().
This means, the renewing of the prefix by the dibbler client will be
failing later.
https://bugs.launchpad.net/neutron/+bug/1639042 reported a symptom
that is also caused by the removal of the bind LLA. Both bugs may
share the same root cause: bind LLA should be preserved until the pd
subnet is removed from the router.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1640271/+subscriptions
Follow ups