[15:48] <holmanb> Olvier67: It looks like minimal helped you out, thanks minimal for picking up the dropped baton :)
[15:58] <minimal> holmanb: yw
[16:12] <holmanb> ryland: Thanks for the update. Do you know whether Salt Cloud actually interacts with cloud-init in any way? A quick grep of the docs don't turn up cloud-init anywhere, which leads me to think my earlier hunch is still on track: the existance of the VMware tools on the image cause cloud-init to incorrectly identify the datasource https://github.com/canonical/cloud-init/blob/main/tools/ds-identify#L940
[16:14] <holmanb> ryland: I'm opening a bug to continue the discussion, if what I just said makes sense (please tell me if I'm overlooking something) then it's a bug
[16:14] <holmanb> ryland: https://bugs.launchpad.net/cloud-init/+bug/1977759
[16:16] <ryland> holmanb, as far as I understand it right now, it looks like salt-cloud is leveraging VMware's VM customization which uses the OVF datasource. I think you are right, it uses OVF by default it seems. When I advise cloud-init to only use the vmware datasource, it does everything correctly from its pov. But then the VM is started without the virtual NIC being connected. This might be an issue with salt-cloud though
[16:17] <ryland> holmanb, is there a way to use two datsources and merge them?
[16:20] <holmanb> ryland: The datasources have some really specific logic in them. I don't think they are composable
[16:23] <ryland> holmanb, it looks to me, like salt-cloud only works properly when I use the OVF datsource, but salt-cloud does not offer me a way to specify userdata when using the vmware driver. but when i use the vmware datsource, and not ovf, then salt-cloud is not enabled the virtual nics properly in the hypervisor level.
[16:23] <ryland> i might have to chose, either use salt-cloud or use cloud-init :(
[16:28] <holmanb> ryland: apologies, I missed the "vnic is missing in guest", I see now that you wrote that already in your gist.
[16:29] <holmanb> agreed, that part of this issue is not a cloud-init bug and not something cloud-init can fix :/
[16:36] <holmanb> ryland: I just updated the launchpad bug with the parts that are actionable for cloud-init. If you happen to file a bug with salt-cloud, feel free to drop a link to it in the launchpad  bug so we can follow the progress.
[16:55] <ryland> holmanb, thank you! yes, that all makes sense. just a correction for the bug report, the virtual nics are there, they are just not activated. i will dig through the salt-cloud code on tuesday to see if i can identify the point where it would need to activate the nics, but does not (for whatever reason). i will also talk to my vmware reps to see if they have something in the pipeline for this that needs to find its way to the oss version of
[16:55] <ryland>  salt, or if i should just go ahead and create a bug with the salt oss project.
[16:56] <ryland> i just realized that today is monday. damn holidays :D i thought its sunday lol
[17:01] <holmanb> I'll update the ticket reflecting the nic status per your correction
[17:01] <holmanb> ryland: no holiday today for me, but enjoy the rest of yours :)
[17:02] <ryland> holmanb, thank you :)