** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878682
Title:
> Ryan,
>
> Thank you so much for taking the time to go over the constraints and
> competing goals. It's always helpful to know what constituencies are
> involved.
Sure.
>
> > That said, I do think that cloud-init can make it easier to enable ipv6
> > where
> > it's desired (but without having
Ryan,
Thank you so much for taking the time to go over the constraints and
competing goals. It's always helpful to know what constituencies are
involved.
> That said, I do think that cloud-init can make it easier to enable ipv6 where
> it's desired (but without having to write your own network
Hi Kevin,
> In the year 2020, IPv6 should be a first class citizen and I should not need
> to provide additional config for it to work right. The issue here is not
> that I can't find a workaround to make my scenarios work. The issue here is
> that I should not need any such workarounds on a
> If you are not providing any network config to cloud-init, current the
default fallback is to DHCP (ipv4) only
This is precisely the bug I am reporting.
> And for ipv6 config, I suspect you'll want to provide an netplan
config with:
In the year 2020, IPv6 should be a first class citizen and I
In your dual stack example, can you run cloud-init collect-logs and
attach the created tarball?
In particular the cloud-init.log and what, if any network configuration
you're supplying in your NoCloud datasource.
> This tells me that someone enabled dhcp4 but not dhcp6 for cloud-init. We
>
Executive summary: I expected this test to go much differently. This bug
should probably be "cloud-init does not wait for IPv6 config in dual-
stack network"
--
One of my initial tests was in my primary dual-stack network, and it
also worked similar to your example.
Excerpt from my deploy
Hi Kevin,
I did some testing and ipv6 seems to work as expected for me. I did the
following:
1. `virsh net-edit default` and added:
to have IPv6 configured on virbr0. As the prefix is a /64 dnsmasq will
automatically send router advertisements on the
