16:01:40 <akasurde> #startmeeting Ansible VMware Working Group Meeting
16:01:40 <zodbot> Meeting started Mon Jul  9 16:01:40 2018 UTC.
16:01:40 <zodbot> This meeting is logged and archived in a public location.
16:01:40 <zodbot> The chair is akasurde. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:01:40 <zodbot> The meeting name has been set to 'ansible_vmware_working_group_meeting'
16:01:46 <akasurde> Hello Everyone
16:10:53 <akasurde> anyone around ?
16:14:27 <bcoca> no, summer!
16:19:23 <akasurde> #chair bcoca
16:19:23 <zodbot> Current chairs: akasurde bcoca
16:22:16 <akasurde> Will wait for next 5 min otherwise close the meeting.
16:24:00 <Lemmons> So I'm here, but mostly to listen.
16:24:24 <akasurde> #chair Lemmons
16:24:24 <zodbot> Current chairs: Lemmons akasurde bcoca
16:24:35 <akasurde> Lemmons, hi would you like to discuss anything ?
16:25:19 <Lemmons> akasurde, I stumbled on this channel trying to get vsphere_guest to work, and dropped in after chasing bug reports for a few hours.
16:25:32 <Lemmons> However... before you ask, I have few details at my fingertips right now.
16:26:11 <akasurde> Cool
16:27:28 <Lemmons> I would say this: I seem to have replicated some issues with vmware_guest at home, and I have a single playbook still relying on vsphere_guest now. Do you know how close feature parity is?
16:27:29 <akasurde> fyi, vsphere_guest is deprecated module
16:27:31 * Lemmons wishes he could be more specific
16:27:49 <Lemmons> akasurde, yep, I joined this channel after seeing some bugs saying I should upgrade, and I was not able to use the new module.
16:28:45 <akasurde> Lemmons, you can file issue if vmware_guest is not usable
16:29:16 <Lemmons> I believe the issue was that provisioning new hosts was not working with the file: directive, and I had discovered a known bug.
16:29:25 <Lemmons> *folder: directive
16:29:36 <Lemmons> I am looking for that bug now, actually.
16:31:45 <Lemmons> akasurde, found it. i stumbled on this at home: https://github.com/ansible/ansible/issues/35943
16:32:21 <Lemmons> I have a dvswitch with many portgroups, but I can not provision a new vm AND make the vnic join the right dvportgroup. So I am using the old module.
16:32:53 <akasurde> old module means vsphere_guest ?
16:33:26 <Lemmons> Yes. I was not able to work around it, but I will try a new attempt and post the results.
16:34:22 <akasurde> Lemmons, vsphere_guest is backed by a deprecated API so we decided to deprecated in 2.5 version and removed in 2.9
16:36:38 <Lemmons> yes, I am worried about when I upgrade at home. For now, this looks like exactly what I'm seeing. I need to get you better details if I'm still seeing this since I have not tried in weeks.
16:36:39 <akasurde> what does vmware_guest returns error ?
16:37:09 <Lemmons> It fails to provision the VM whenever I pass the new nic a dvportgroup. But, I admit I don't have details right now. I'll pop back in with more useful logs!
16:38:00 <akasurde> Lemmons, definitely
16:38:07 <akasurde> that will certainly help
16:39:33 <akasurde> btw, what is ansible and vcenter version ?
16:39:59 <Lemmons> vcsa 6.5, esxi 6.0, ansible... unsure, but should be very recent (should be...)
16:40:55 <akasurde> vcenter version looks good, but ansible version will play important rolve
16:40:57 <akasurde> role*
16:41:08 <akasurde> lot of bugs got fixed in 2.5 and onwards
16:41:18 <Lemmons> Okay, perhaps I have no updated this recently enough and you quietly fixed this all when I was not looking :)
16:42:25 <akasurde> it would be worth trying :)
17:04:38 <akasurde> #endmeeting