[14:43] <do3meli> hi 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:49] <Odd_Bloke> do3meli: That doesn't sound familiar to me.  Could you file a bug using the link in the topic, please?
[14:52] <do3meli> @Odd_Bloke: seems they have 18.3-6 version pre-installed in the image. maybe an issue with that one ?
[14:52] <Odd_Bloke> Could be!
[14:52] <Odd_Bloke> If you can try with a more recent version, that'd be really helpful.
[14:52] <Odd_Bloke> (testing and unstable have 19.2.)
[14:53] <do3meli> is there a .deb package around somewhere for easy upgrade ?
[14:58] <Odd_Bloke> do3meli: You could grab it off a Debian mirror
[14:58] <Odd_Bloke> ?
[14:58] <do3meli> never mind. i found one.
[15:24] <do3meli> Odd_Bloke: here we go: https://bugs.launchpad.net/cloud-init/+bug/1846513
[15:25] <ubot5> Launchpad bug 1846513 in cloud-init "debian 10 cloud-init stuck in systemd-networkd after 1. reboot" [Undecided,New]
[15:28] <Odd_Bloke> do3meli: 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 bug
[15:29] <do3meli> sure 1 sec
[15:29] <blackboxsw> bah Odd_Bloke beat me
[15:29] <blackboxsw> ... again
[15:30] <do3meli> done
[15:32] <Odd_Bloke> do3meli: Do you have a working OpenStack metadata service?
[18:18] <rharper> Odd_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/1821102
[18:18] <ubot5> Launchpad bug 1821102 in cloud-init "Cloud-init should not setup ephemeral ipv4 if apply_network_config is False for OpenStack" [High,Fix released]