If anything, this is fallout due to the bug you mention. LXD should be explicit; as should cloud-init.
On Mon, Feb 26, 2018 at 10:07 AM, Scott Moser <ssmoser2+ubu...@gmail.com> wrote: > So this *will* cause a change in behavior in all lxd guests. > > $ lxd file pull b1/var/lib/cloud/seed/nocloud-net/network-config - > version: 1 > config: > - type: physical > name: eth0 > subnets: > - type: dhcp > control: auto > > > nothing there says we *should* have ipv6, yet I do have ipv6 enabled. > > $ lxc network show lxdbr0 > config: > ipv4.address: 10.145.210.1/24 > ipv4.nat: "true" > ipv6.address: fd42:6470:c1cd:249f::1/64 > ipv6.nat: "true" > description: "" > name: lxdbr0 > type: bridge > used_by: > - /1.0/containers/a1 > - /1.0/containers/b1 > - /1.0/containers/b2 > - /1.0/containers/bb > - /1.0/containers/x1 > managed: true > > $ lxc list | grep b1 > | b1 | RUNNING | 10.145.210.39 (eth0) | > fd42:6470:c1cd:249f:216:3eff:fe95:9c7c > (eth0) | PERSISTENT | 0 | > > > Related bugs > https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1732002 > > -- > https://code.launchpad.net/~raharper/cloud-init/+git/ > cloud-init/+merge/339437 > You are the owner of ~raharper/cloud-init:fix/netplan-accept-ra-off. > -- https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339437 Your team cloud-init commiters is requested to review the proposed merge of ~raharper/cloud-init:fix/netplan-accept-ra-off into cloud-init:master. _______________________________________________ Mailing list: https://launchpad.net/~cloud-init-dev Post to : cloud-init-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~cloud-init-dev More help : https://help.launchpad.net/ListHelp