do3melihi there - just a qq: is it a known problem that cloud-init in the debian 10 cloud image is not working as expected after first reboot after deployment. sytemd-networkd seems to be trying to bring up network which takes around 6 min until it times out.14:43
Odd_Blokedo3meli: That doesn't sound familiar to me.  Could you file a bug using the link in the topic, please?14:49
do3meli@Odd_Bloke: seems they have 18.3-6 version pre-installed in the image. maybe an issue with that one ?14:52
Odd_BlokeCould be!14:52
Odd_BlokeIf you can try with a more recent version, that'd be really helpful.14:52
Odd_Bloke(testing and unstable have 19.2.)14:52
do3meliis there a .deb package around somewhere for easy upgrade ?14:53
Odd_Blokedo3meli: You could grab it off a Debian mirror14:58
do3melinever mind. i found one.14:58
do3meliOdd_Bloke: here we go: https://bugs.launchpad.net/cloud-init/+bug/184651315:24
ubot5Launchpad bug 1846513 in cloud-init "debian 10 cloud-init stuck in systemd-networkd after 1. reboot" [Undecided,New]15:25
Odd_Blokedo3meli: OK, we're gonna need at least cloud-init.log from there to debug further.  Can you run `cloud-init collect-logs` and attach the tarball to the bug?15:28
blackboxsw+1 Odd_Bloke do3meli was just commenting that on the bug15:28
do3melisure 1 sec15:29
blackboxswbah Odd_Bloke beat me15:29
blackboxsw... again15:29
Odd_Blokedo3meli: Do you have a working OpenStack metadata service?15:32
rharperOdd_Bloke: that looks like this one, where the ephemeral dhcp didn't setup the classless staci routes, but after "fallback dhcp" comes up, crawling IMDS works;  https://bugs.launchpad.net/cloud-init/+bug/182110218:18
ubot5Launchpad bug 1821102 in cloud-init "Cloud-init should not setup ephemeral ipv4 if apply_network_config is False for OpenStack" [High,Fix released]18:18

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!