Control: retitle -1 cloud-init should depend on dhcpcd-base rather than dhcpcd Control: severity -1 important
On Fri, Sep 27, 2024 at 10:47:05PM +0200, Bastian Blank wrote: > After the cloud-init run, a dhcpcd keeps running and regularly redoing > the network config: > > | Sep 27 20:40:01 boot1 dhcpcd[686]: eth0: pid 1 deleted default route via > fe80::1234:5678:9abc > | Sep 27 20:40:01 boot1 dhcpcd[686]: eth0: pid 1 deleted route to > 2ef:2dfd:ea32:2::/64 > | Sep 27 20:40:06 boot1 dhcpcd[686]: eth0: adding route to > 2ef:2dfd:ea32:2::/64 > | Sep 27 20:40:06 boot1 dhcpcd[686]: eth0: adding default route via > fe80::1234:5678:9abc > > cloud-init must make sure it is only used in one-shot and killed > afterwards. Based on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082898, it seems that cloud-init should depend on dhcpcd-base rather than dhcpcd, and the cloud-images should ensure that only -base is installed. noah
