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
> need to make sure we have feature parity across the protocols.
If you are not providing any network config to cloud-init, current the
default fallback is to DHCP (ipv4) only; Ubuntu itself defaults to
accepting IPv6 RAs, but asynchronously from boot.
And for ipv6 config, I suspect you'll want to provide an netplan config
with:
network:
version: 2
ethernets:
primary:
match:
macaddress: 52:54:00:4d:27:e9
dhcp4: true
dhcp6: true
accept-ra: yes
Which ensures that systemd-networkd-wait-online.service will wait the
required time for querying and accepting any RA.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
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:
IPv6 not enabled by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1878682/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
