[13:45] <boolman> hey, cloud-init runs to early for me. is there any way to delay it?
[14:37] <Odd_Bloke> boolman: Could you expand on the problem you're trying to solve?
[14:42] <boolman> Odd_Bloke: yeah sure, I have no issues at all running cloud-init for example on openstack vms. however, Im trying to get it to work on vmware, and I believe vmware is really slow to set the network configuration. so cloud-init is already done before it gets network access
[14:43] <boolman> so this is installed on my vm template: https://github.com/vmware/cloud-init-vmware-guestinfo which allows me to send userdata and metadata to the vm during deploy ( terraform in my case )
[14:46] <Odd_Bloke> boolman: OK, that's useful information.  What specifically is failing?  (cloud-init _could_ happily use the guestinfo without networking, I think, so I'm guessing that there's userdata or somesuch that is breaking?)
[14:47] <boolman> I've disable networking through cloud-init, network: { config: disabled }
[14:48] <boolman> what is failing is basically everything that requires network, so apt_update, packages: [], bootcomd: [ ping -c 1 8.8.8.8 ]
[14:51] <Odd_Bloke> OK, and what distro/version is this, and how did you install cloud-init?
[14:52] <boolman> ubuntu bionic, apt-get install cloud-init
[14:53] <Odd_Bloke> Most Ubuntu cloud images already have cloud-init installed; how are you creating your image?
[14:53] <boolman> this was built from an cd iso
[14:54] <boolman> dont think I can run cloud images on vmware
[14:55] <Odd_Bloke> http://cloud-images.ubuntu.com/releases/bionic/release/ has a variety of images (including a VMDK and an OVA), so you might want to consider using those (if changing the image source is an option).
[14:55] <Odd_Bloke> How is networking being configured if not by cloud-init?
[15:07] <boolman> https://www.terraform.io/docs/providers/vsphere/r/virtual_machine.html#cloning-and-customization-example
[15:07] <boolman> the network_interface {} block
[15:13] <Odd_Bloke> boolman: Hm, OK, I'm not familiar with that.  Does that actually generate network configuration inside the guest, or is it just configuring the devices that will be presented to the guest?
[15:13] <boolman> yes it works, just not during the cloud-init's lifetime
[15:17] <Odd_Bloke> Do you know how it writes out its network configuration?  Ubuntu's boot has systemd-networkd-wait-online.service, which waits for networking before proceeding, and the network-dependent parts of cloud-init run after that.
[15:17] <Odd_Bloke> So I would expect it to work regardless, but perhaps the network is configured after that point?
[15:17] <Odd_Bloke> boolman: Do you have files in /etc/netplan/... ?
[17:18] <blackboxsw> rharper: minor doc suggestions on https://github.com/CanonicalLtd/uss-tableflip/pull/31 I put up https://github.com/CanonicalLtd/uss-tableflip/pull/32  as well
[17:18] <rharper> thanks
[20:29] <boolman> my vm boots and network is fine.
[20:29] <wyoung> Nice work
[23:14] <blackboxsw> ahosmanMSFT: sorry, I'm finally poking at Azure CI tests now not seeing the timeout error so far. will give it a few runs and see if I can see it.
[23:15] <ahosmanMSFT> blackboxsw: Thanks, when issue was running multiple tests at once the issue occurs due to self._img_instance having different values in images.py on azurecloud platform. Also ssh time out issues due to wait_for_cloud_init function.
[23:16] <blackboxsw> ahosmanMSFT: you mean at once (in parallel) or serially running through the whole test suite?
[23:17] <blackboxsw> I'm guessing serially running the whole suite right
[23:17] <ahosmanMSFT> yes
[23:17] <blackboxsw> ok thx. will give it a couple runs
[23:18] <ahosmanMSFT> Those issues occur at the same time, I was able to debug and find them seperately
[23:18] <ahosmanMSFT> but the ssh one only effects time out
[23:19] <ahosmanMSFT> the other issue (self._img_instance not updating) effects image building, so no snapshots