[00:35] <compufreak> Is there a better way to identify disks for disk_setup with kvm/libvirt than disk #1=/dev/sda, disk #2=/dev/sdb. They're setup as scsi disks on virtio-scsi controller
[01:45] <minimal> compufreak: you *might* be able to use /dev/disk/by-* entries instead, not sure
[01:55] <compufreak> yeah, looks like maybe I can set serial= with the virt-install --disk flag then something more stable comes up in by-uuid
[01:56] <compufreak> That got me /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_<serial string>
[07:08] <jwoodard80> Hello all.... I'm trying to use the "device_aliases" and having a bit of trouble. I've setup "database_drive: /dev/sdf" in the config. On boot, I show updated device entry as expected, however, it does not partition and states "Device does not exist and was not created with a udevadm settle"  .... I was under the impression that defining the alias
[07:08] <jwoodard80> would set the device in /dev but am I wrong in this?
[10:02] <yziquel> Just cloned cloud-init. How do I build it ? I just typed "make" and I got "Error: read-version version '23.4.-201-somesha' not equal to code version ''23.4.3'"
[10:46] <yziquel> My /run/cloud-init/network-config.json is not generated. Why could that be ?
[10:50] <aciba> hello yziquel, not sure what's your use case, but cloud-init is preinstalled in cloud images and runs on first boot. The network config is not generated after running make.
[10:50] <aciba> are you trying to generate a golden image or something in those lines, or what is your use case?
[10:52] <yziquel> aciba my use case is the following. I used incus vm ubuntu/cloud to perform a disaster recovery of a machine whose cpu died. I mount everything into a somewhat usable incus vm. I'm now trying to set up networking so that this incus vm get an IP from outer LAN DHCP. When manually altering netplan, I do get an IP. However, cloud-init does not do it
[10:52] <yziquel> for me no matter what configuration I am trying. So I am now trying to understand how cloud-init works and I am observing that the documentation says the networking data should be output in /run/cloud-init/network-config.json on that VM, and it is not.
[14:47] <falcojr> yziquel: are you looking at the right version of the docs? network-config.json is new in 23.4, but the version in ubuntu images should still be 23.3
[14:48] <falcojr> more generally, a pastebin of /var/log/cloud-init.log might help us understand the problem
[14:50] <yziquel> falcojr i'll try to get around to double checking that.
[14:57] <yziquel> falcojr indeed. I'm on 23.3.
[16:51] <minimal> jwoodard80: defining the alias simply means that that alias can be then be used elsewhere in disk_setup and fs_setup configuration. The device that you are mapping to has to exist (cloud-init does not create devices) and error you quoted indicates that /dev/sdf does not exist.
[19:22] <jwoodard80> minimal Thank you so much! I figured that would be the answer but I wanted to confirm.
[22:50] <SuperLag> I'm trying to pass user-data to TF to add it to an EC2 instance and it's not working. https://termbin.com/gilz 
[22:51] <SuperLag> the only recent edit I'd made was the pipe after ssh_authorized_keys
[22:52] <SuperLag> and it didn't help