I launch a centos/7/cloud image each morning at 05:00 UTC. Starting today it was taking over 1 minute for the systemd startup to complete. The delay seemed to be errors obtaining IPv6 DHCP address. I have reproduced this on the lxd tryit server:
root@tryit-generous:~# lxc launch images:centos/7/cloud fluffy
Creating fluffy
Starting fluffy
root@tryit-generous:~# lxc exec fluffy -- journalctl -f
-- Logs begin at Wed 2021-03-17 06:39:09 UTC, end at Wed 2021-03-17 06:40:17 UTC. --
Mar 17 06:39:09 fluffy systemd-journal[63]: Runtime journal is using 8.0M (max allowed 196.5M, trying to leave 294.8M free of 1.9G available → current limit 196.5M).
Mar 17 06:39:09 fluffy systemd-journal[63]: Journal started
...
Mar 17 06:39:43 fluffy dhclient[317]: RCV: Advertise message on eth0 from fe80::216:3eff:fee7:7fc0.
Mar 17 06:39:43 fluffy dhclient[317]: message status code NoAddrsAvail: "no addresses available"
Mar 17 06:40:14 fluffy dhclient[317]: Max retransmission duration exceeded.
Mar 17 06:40:14 fluffy network[118]: Determining IPv6 information for eth0... failed.
Mar 17 06:40:14 fluffy network[118]: WARN : [/etc/sysconfig/network-scripts/ifup-eth] Unable to obtain IPv6 DHCP address eth0.
Mar 17 06:40:14 fluffy /etc/sysconfig/network-scripts/ifup-eth[339]: Unable to obtain IPv6 DHCP address eth0.
Mar 17 06:40:14 fluffy network[118]: [ OK ]
...
Mar 17 06:40:17 fluffy systemd[1]: Reached target Cloud-init target.
Mar 17 06:40:17 fluffy systemd[1]: Startup finished in 1min 8.735s.
I launch a centos/7/cloud image each morning at 05:00 UTC. Starting today it was taking over 1 minute for the systemd startup to complete. The delay seemed to be errors obtaining IPv6 DHCP address. I have reproduced this on the lxd tryit server:
Full journal: journal.txt
I've switched my project to using the centos/7 (non cloud-init) image, which doesn't have this issue: