Gavin Williams wrote:

Currently I'm trying to setup a Foreman 1.5.2 install on CentOS 6 against a vSphere 5.1.0 installation.

The compute resource was created without any issues.
However when I try and create a new host, I get an error:
[...]

Have tried to enable debugging, however am unable to get logging working.

Production.log excerpt is here: http://pastebin.com/zP5TgezT

Let me know if can provide any further info.

Hi Could let know how you sorted this out ?? Iam running foreman 1.10 with Vcenter 4.1 and the VM gets created but foreman returns the same error.

When I check the VM the customisation for respective memory or nic's haven't been done as well..

John Moses wrote:

Gavin Williams wrote:

Currently I'm trying to setup a Foreman 1.5.2 install on CentOS 6 against a vSphere 5.1.0 installation.

The compute resource was created without any issues.
However when I try and create a new host, I get an error:
[...]

Have tried to enable debugging, however am unable to get logging working.

Production.log excerpt is here: http://pastebin.com/zP5TgezT

Let me know if can provide any further info.

Hi Could let know how you sorted this out ?? Iam running foreman 1.10 with Vcenter 4.1 and the VM gets created but foreman returns the same error.

When I check the VM the customisation for respective memory or nic's haven't been done as well..

I never did get it fixed TBH...

Gavin Williams wrote:

John Moses wrote:

Gavin Williams wrote:

Currently I'm trying to setup a Foreman 1.5.2 install on CentOS 6 against a vSphere 5.1.0 installation.

The compute resource was created without any issues.
However when I try and create a new host, I get an error:
[...]

Have tried to enable debugging, however am unable to get logging working.

Production.log excerpt is here: http://pastebin.com/zP5TgezT

Let me know if can provide any further info.

Hi Could let know how you sorted this out ?? Iam running foreman 1.10 with Vcenter 4.1 and the VM gets created but foreman returns the same error.

When I check the VM the customisation for respective memory or nic's haven't been done as well..

I never did get it fixed TBH...

This is now gonna be a nightmare as we were our provisioning plans thru foreman are now at halt.. :-(

what's the status here with newer Foreman versions?

Michael Moll wrote:

what's the status here with newer Foreman versions?

I can report that this issue still exists on Foreman 1.11.1. Currently deployed a PoC with RHEL 6.7 against a vSphere 4.1 cluster.

Creating a new host will result in an initial VM creation in the correct folder and resource pool, but stops with a 1 vCPU, 32MB RAM VM with no NIC or Storage. All other options are not set, including hot plug. Viewing the VM (or any other VM for that matter) through Compute Resources > Virtual Machine or Associating VMs also results in the same error, though with a slightly different error message:

RbVmomi::Fault
InvalidProperty:

Something I'd like to note, but not sure if it's relevant: Recent releases of fog-vsphere included the addition of the property "config.hardware.numCoresPerSocket" (located in /opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-0.6.3/lib/fog/vsphere/compute.rb). vSphere 4.1 API doesn't have this property, as that was introduced in vSphere 5. It's possible there are more properties that are being mapped that don't exist pre-5.5.

A similar issue was posted at fog-vsphere (since closed): https://github.com/fog/fog-vsphere/issues/2