=== TheMetz1 is now known as TheMetz
=== cpaelzer_ is now known as cpaelzer
[13:56] <dalurka> I wonder if anybody might know where I can find the scripts that generate the initrd on the live iso?
[13:57] <dalurka> (I'm asking because I'm trying to pxe from a usb-c nic and the drivers are not packaged in. it works fine if I patch the initrd by hand. I can't see why those drivers should not be included by default)
[13:59] <dalurka> any pointers where to look?
[14:06] <falcojr> TheMetz: I responded to the launchpad bug, but that looks like something else on boot is preventing one of the cloud-init services from starting
[14:09] <falcojr> dalurka: that's not really a cloud-init question, but I don't know where else you should ask
[14:09] <dalurka> yea, I know.. this was the closest I could think
[14:10] <dalurka> :(
[14:25] <dalurka> asked in #ubuntu-kernel might be wrong as well :)
[14:49] <TheMetz> falcojr:  Thank you for the follow up.  It looks like 'cloud-config.service' isn't set to startup on boot. 
[14:49] <TheMetz> I enabled the service and testing now.
[15:30] <akutz> Hey falcojr and blackboxsw, I just sent you both an e-mail. I normally don't text-to-alert-of-e-mail, but this is *possibly* time sensitive, so I wanted to make sure y'all saw it. Thanks!
[15:31] <falcojr> akutz: thanks, we'll take a look
[15:31] <akutz> Ack, thanks!
[16:08] <TheMetz> falcojr:  I'm still having the same issue after enabling 'cloud-config.service' in systemd.
[16:09] <falcojr> TheMetz: there's also a cloud-final.service
[16:10] <falcojr> but...those should all be enabled when cloud-init is installed
[16:10] <falcojr> or on the image
[16:10] <falcojr> if they're not and nothing has been modified, that points to an issue in the packaging
[16:12] <TheMetz> Are there any other services that should be enabled?
[16:17] <foxxx0> hi, is there any way to trigger NoCloud (without configdrive) network re-configuration without needing to reboot? I.e. the relevant V2 network config in my /etc/cloud/cloud.cfg.d/99-my-network.cfg has been updated. I'm seeing "stages.py[DEBUG]: No network config applied. Neither a new instance nor datasource network update on 'System boot' event" in the log
[16:47] <falcojr> TheMetz: if cloud-init-local.service and cloud-init.service are already enabled, no, that should be the last one
[16:47] <falcojr> see https://cloudinit.readthedocs.io/en/latest/topics/boot.html#
[16:48] <dalurka> falcojr: got help by xnox over there! yaay!
[16:53] <TheMetz> falcojr: That worked.  After enabling cloud-final.service it started working as expected.
[16:54] <TheMetz> Thank you for your help.
[18:13] <EugenMayer> how to find out which cloud-init version for network configuration e.g. debian bullseye generic cloud supports?
[20:21] <blackboxsw> EugenMayer:https://packages.debian.org/search?suite=bullseye&arch=any&searchon=names&keywords=cloud-init shows me cloud-init 20.4  is in bullseye. Readthedocs for 20.4 tells me that both network config v1 and v2 are supported on cloud-init 20.4 https://cloudinit.readthedocs.io/en/20.4/topics/network-config.html
[20:21] <blackboxsw> not sure if I misread your question though. What problem are you trying to solve?