Verification-done for xenial with nplan 0.29~16.04.1:
The bug this is fixing is a regression in 0.26~16.04.1, which is a version that only landed in -proposed. 0.23~16.04.1 (the previous released nplan) does not show this bug, and 0.29~16.04.1 does not show IPv6 issues.
I set up a container with the new nplan version, verified that once netplan is configured the container can successfully get both an IPv4 and IPv6 address; which is displayed in 'lxc ls' on the host.
Verification-done for xenial with nplan 0.29~16.04.1:
The bug this is fixing is a regression in 0.26~16.04.1, which is a version that only landed in -proposed. 0.23~16.04.1 (the previous released nplan) does not show this bug, and 0.29~16.04.1 does not show IPv6 issues.
I set up a container with the new nplan version, verified that once netplan is configured the container can successfully get both an IPv4 and IPv6 address; which is displayed in 'lxc ls' on the host.