[08:06] <smoser> cpaelzer: are you able to recreate https://bugs.launchpad.net/cloud-init/+bug/1750770
[08:06] <ubot5`> Ubuntu bug 1750770 in cloud-init "installing cloud init in vmware breaks ubuntu user" [Undecided,New]
[08:06] <smoser> it must have been 16.04, right >
[08:24] <do3meli> smoser: good morning, can you trigger another ci run for https://code.launchpad.net/~d-info-e/cloud-init/+git/cloud-init/+merge/340112 ?
[08:42] <blackboxsw> morning do3meli https://jenkins.ubuntu.com/server/job/cloud-init-ci/827/ running
[08:43] <do3meli> thx blackboxsw
[08:43] <blackboxsw> btw thanks for working on this. much appreciated
[08:57] <do3meli> thanks blackboxsw, btw ci run completed successfully. so this is finally really ready for merging now
[09:07] <blackboxsw> do3meli: looks great. I'm working on an automated lander this morning and I'll run it against your branch. You'll probably see it close in the new few minutes
[09:08] <do3meli> awesome ;-)
[09:08] <do3meli> may you want to set it to approved before your automation picks it up ;-) cause currently the MP status is WIP
[09:08] <do3meli> i mean "needs review"
[10:37] <blackboxsw> smoser: rharper https://askubuntu.com/questions/259453/how-can-i-monitor-cloud-init-for-errors-and-trigger-a-script-when-it-fails/1012766#1012766
[10:43] <rharper> maybe combine those together?
[10:43] <rharper> cloud-init status --wait and then examine the result.json file
[10:51] <smoser> blackboxsw: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/341116
[11:02] <do3meli> can someone look into https://code.launchpad.net/~d-info-e/cloud-init/+git/cloud-init/+merge/340757 ?
[14:00] <smoser> rahbug 1749696
[14:00] <smoser> rharper: bug 1749696
[14:00] <ubot5`> bug 1749696 in cloud-init "Excessively vague error while parsing yaml: RuntimeError: Unable to shellify type dict which is not a list or string" [Undecided,Incomplete] https://launchpad.net/bugs/1749696
[14:00] <smoser> we could mark my shellify change as fixing that.
[14:00] <smoser> but..
[14:17] <PsyRabbit> smoser: I'm using open-vm-tools and I would like to know what data comes via OVF into my machine from VCloud director. So I red some source but didnt find files like cust.cfg or nics.txt referenced here: https://github.com/cloud-init/cloud-init/blob/master/cloudinit/sources/DataSourceOVF.py#L112 Is it only for vmware tools? Or how can I see all data which is provided by VCloud Director OVF inside my
[14:17] <PsyRabbit> machine?
[14:35] <smoser> PsyRabbit: what do you mean "via OVF" ?
[14:36] <smoser> is that via CD-rom / iso ?
[14:36] <smoser> or via the guest/host vmware transport
[14:37] <smoser> most of the vmware code is contributed via vmware developers and embarassingly I've never actually used it myself.
[14:37] <smoser> I have used the OVF iso transport, and originally wrote and tested that.
[14:39] <PsyRabbit> It's via the guest/host vmware transport... The documentation is really thin in this direction
[14:47] <smoser> PsyRabbit: yeah. i really have very little vmware knowledge.
[14:50] <PsyRabbit> Okay... I mean I see that the hostname etc. can change, so the transport itself is working. But is there a way that I can dump all incoming key->value pairs independently from my datasource? Just that I know what I can use for further setup tasks?
[14:51] <PsyRabbit> It's not really transparent for me...
[14:52] <smoser> PsyRabbit: i'm really sorry, you're at the limits of my knowledge in this area.
[14:53] <blackboxsw> PsyRabbit: yeah around this space, I know that I recently reviewed a vmware branch that dealt with placing some customization script seeded (I thought from https://code.launchpad.net/~msaikia/cloud-init/+git/cloud-init/+merge/330105) It has a bit more context on a single customization script file containing both Pre and Post customization operations which gets placed on the system.
[14:53] <blackboxsw> from the looks of the datasourceOVF, that file is located at /var/run/vmware-imc
[14:53] <PsyRabbit> smoser: Thank you anyway :/ No problem, maybe someone read our conversation :) But I really have to say the documentation needs improvement...
[14:54] <blackboxsw> on a deployed system. best approach (because most vmware folks only infrequently join this channel is to go for a deployment and check that directory for content.
[14:54] <blackboxsw> also you can find a bunch of information on which cloud-init reacts (user-data/metadata) in /run/cloud-init/instance-data.json on a deployment that contains cloud-init 17.1 or later
[14:55] <PsyRabbit> blackboxsw: The file is not present - I have the path from the source... Maybe it's deleted after usage (didnt find rm statement in python) or open-vm-tools is working different than vmware tools.
[14:57] <PsyRabbit> Hmm, I'm using cloud-init 0.7.9 which is from the rhel 7 repo... instance-data.json is not present, there is only result.json and status.json
[14:59] <blackboxsw> from wait_for_imc_cfg_file() in DatasourcOVF it looks like that file is optional as that function which if memory serves I think only is written if custome user scripts were provided during vm creation
[14:59] <blackboxsw> PsyRabbit: let me get you a link to our tip COPR repo... one sec
[14:59] <blackboxsw> it'd give you the ability to upgrade to latest cloud-init to check
[15:01] <blackboxsw> PsyRabbit: https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/
[15:01] <blackboxsw> we have jobs that update this repo with tip of cloud-init (currently revision 18.1...)
[15:02] <PsyRabbit> blackboxsw: Thank you, I will try it out :)
[15:02] <blackboxsw> running 'sudo cloud-init clean --logs --reboot' after you install that should clean your system of cloud-init artficts and reboot it allowing cloud-init to attempt running again
[15:03] <blackboxsw> after reboot, the OVF datasource  will write /run/cloud-init/instance-data.json which sheds light on metadata/user-data that cloud-init reacts too
[15:04] <blackboxsw> also PsyRabbit vmware folks occasionally jump into our cloud-init bi-weekly status meeting
[15:04] <blackboxsw> oops let me update that in the channel topic
[15:05] <PsyRabbit> I think you helped me a lot blackboxsw! Thank you
[15:06] <blackboxsw> no worries
[18:20] <dojordan> hey @blackboxsw, you threre?
[19:57] <dojordan> hey all, on bionic, how / when does /etc/resolv.conf get generated?
[23:10] <dojordan> @smoser, when you get a chance: https://code.launchpad.net/~dojordan/cloud-init/+git/cloud-init/+ref/fix_azure_hostname