[13:06] <m00c0w> Hi! I'm new to using cloud-init and I have success with CentOS 7.  But when I try to spin up Ubuntu 18.04 using the CLoudImage I end up with KVM console saying that there is no boot partition. Is anything special required to do cloud-init with kvm/Ubuntu Bionic other than converting the img file to qcow2?
[13:36] <smoser> m00c0w: that seems unlikely related to cloud-init
[13:36] <smoser> i suspect you have an entry in /etc/fstab that is not right.
[13:37] <smoser> fwiw, i would always using offiicial downloadable images from cloud-images.ubuntu.com
[13:37] <smoser> if you have to modify them, I'd suggest modifying the images rather than building yourself elsewhere.
[13:38] <smoser> caribou: do you need anything from me ?
[16:28] <m00c0w> smoser: I figured it out. There are many different cloud images available for Ubuntu and while the filename was the exact same for the image I had, it was found in the wrong folder on the mirror site. Took a while to figure out
[16:34] <m00c0w> m00c0w: https://paste.ee/p/4tHJ9    Confusing, right? ;)
[18:08] <smoser> powersj: i want to run https://jenkins.ubuntu.com/server/job/cloud-init-integration-lxd-c
[18:08] <smoser> against https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/351371
[18:08] <smoser> in order to catch bug 1783198
[18:08] <smoser> any thoughts on how best to do that ?
[18:09] <powersj> https://github.com/CanonicalLtd/server-jenkins-jobs/blob/master/cloud-init/integration-lxd.yaml#L56
[18:10] <smoser> powersj: well, i want to run it on on c-i hardware
[18:10] <smoser> i've not caught the failure here.
[18:10] <powersj> you have ssh to torkoal ;)
[18:10] <smoser> thats fine
[18:11] <powersj> would you prefer a debug job? like we do for vmtest
[18:11] <smoser> i guess that'd be nice. but i'm ok for now to just run on taht system.