kitchen destroy stopped working on kitchen-vcenter about rbvmomi

[jrgarcia]

I'm not sure what you're referring to with it being the last in a food-chain. Are you saying that the underlying problem with test-kitchen may be caused by rbvmomi? I'll take a look at the problem you're having with kitchen-vcenter and see if I can figure out what's going on.

[nimDevOps]

Thanks for the fast response.
I think it might be related to vmware version upgrade from 6.5 to 6.7 on our farm.

[jrgarcia]

Ok. There shouldn't be any problems moving from vSphere 6.5 to 6.7 with rbvmomi. I'll take a look at your issue and see if I can figure out what's going on.

[nimDevOps]

Thanks,

[nimDevOps]

I've just tested brand new configuration based on your new kitchen-vcenter (2.4.0) driver comparing to previous kitchen-vcenter (1.4.2) . Once I fixed libcurl issue with workaround here chef-boneyard/chef-dk#2025, kitchen destroy worked fine.

Here is a diff of chef gem list:
[New configuration, extra gems]:

• ethon (0.12.0)
• typhoeus (1.3.1)
• vsphere-automation-cis (0.1.0)
• vsphere-automation-content (0.1.0)
• vsphere-automation-sdk (0.1.0)
• vsphere-automation-vapi (0.1.0)
• vsphere-automation-vcenter (0.1.0)

Same gems, different versions:

[old]

• kitchen-vcenter (1.4.2)
• vsphere-automation-sdk (6.6.1)[unofficial, build from source]

[new]

• kitchen-vcenter (2.4.0)
• vsphere-automation-appliance (0.1.0)

On both configurations rbvmomi (1.13.0) so this is not the case for this gem, but somewhere between vsphere-automation-* and kitchen-vcenter.

I will try to migrate to kitchen-vcenter 2+ solution once libcurl issue is resolved.
Thanks again,

[jrgarcia]

The vsphere-automation-sdk does use typhoeus which depends on ethon. I need to modify the templates in that SDK to just use Net::HTTP so there are no dependencies. I'll see if I can help dig in to see what's going on with ethon. Moving to Net::HTTP won't happen very quickly because that's kind of a big change, but I'll definitely make that a higher priority.

[jrgarcia]

I'm going to go ahead and close this issue since the problem isn't with rbvmomi at all, but I'll create a new issue for the vSphere Automation SDK to replace Typhoeus usage with Net::HTTP. Thanks for reporting! I was unaware of this issue until you brought it to my attention!