Timo Goebel

@lzap: This looks like something you might enjoy reviewing. :-)

@ekohl: Sounds good. I think the rails way is the proper choice. We just have to make sure we don't introduce a security vulnerability. Another thing to consider regarding reverse...

> but skipping tests if proxmox is not available does make sense to me. I believe we do something similar in foreman_dlm. https://github.com/dm-drogeriemarkt/foreman_dlm/blob/ca43f537d62235969fe64494684f0ca4232e8768/test/models/host_monitoring_test.rb#L9

@timogoebel, FWIW I'm in favor of removing codeclimate.

Looking at the stack trace and foreman code, it seems to leave the foreman code when calling "vm.mac". This calls "mac" on the fog vsphere server model. In fog we...

To debug this, I'd suggest adding some debug code here: https://github.com/fog/fog-vsphere/blob/ac775b6d0eea0e7e015a992acb3b92eb185c9054/lib/fog/vsphere/models/compute/interfaces.rb#L20 Something like: ```ruby raise "interfaces should have vm or template, got: #{server.class}" ```

Basically, ruby is having issues looking up this constant. Can you provide a stack trace to figure out in which context this is happening?

@lhw: That looks interesting. Do you mind sending PRs for fog-vsphere and Foreman? I'll be happy to review and merge them.

@Zugschlus: Sorry for the long turnaround here. It's possible to activate a debug mode in `rbvmomi` (the library used for connections with vsphere) through `fog-vsphere`: ```ruby client = ::Fog::Compute.new( :provider...

Thanks, @ananace.