21bb776670
When starting the dhcp-agent after an upgrade, there could be stale IPv6 addresses in the namespace that had been configured via SLAAC. These need to be removed, and the same address added back statically, in order for the agent to start up correctly. To avoid the race condition where an IPv6 RA could arrive while we are making this change, we must move the call to disable RAs in the namespace from plug(), since devices may already exist that are receiving packets. Uncovered by the grenade tests. Change-Id: I7e1e5d6c1fa938918aac3fb63888d20ff4088ba7 Closes-bug: #1627902
20 lines
764 B
YAML
20 lines
764 B
YAML
---
|
|
prelude: >
|
|
IPv6 addresses in DHCP namespaces will now be
|
|
(correctly) statically configured by the DHCP agent.
|
|
fixes:
|
|
- There is a race condition when adding ports in
|
|
DHCP namespaces where an IPv6 address could be
|
|
dynamically created via SLAAC from a Router
|
|
Advertisement sent from the L3 agent, leading to
|
|
a failure to start the DHCP agent. This bug has
|
|
been fixed, but care must be taken on an upgrade
|
|
dealing with any possibly stale dynamic addresses.
|
|
For more information, see bug
|
|
`1627902 <https://launchpad.net/bugs/1627902>`_.
|
|
upgrade:
|
|
- On upgrade, IPv6 addresses in the DHCP namespaces
|
|
that have been created dynmically via SLAAC will be
|
|
removed, and a static IPv6 address will be added
|
|
instead.
|