any chance you can turn on debugging (see in troubleshooting) and paste the same output?

hmm.. did you restart and tried to do the same action again? I cant see it in the logs?

Ohad Levy wrote:

hmm.. did you restart and tried to do the same action again? I cant see it in the logs?

Yes, but had not uploaded the log yet :)

which kind of vmware are you do you have clusters support? (the trace shows it fails listing the clusters).

do you have any localization version of vmware etc? did it ever worked with foreman?

Ohad Levy wrote:

which kind of vmware are you do you have clusters support? (the trace shows it fails listing the clusters).

do you have any localization version of vmware etc? did it ever worked with foreman?

VMWare Esxi 5.0.0 managed by VSphere (VMware vCenter Server 5.0.0.16964) First list of the BUG Desription :)
Cluster is named thuis. (dutch for home) My whole setup is running on wmware-workstation 9.0.2
Same setup does work with foreman 1.1

Ronny M wrote:

Ohad Levy wrote:

which kind of vmware are you do you have clusters support? (the trace shows it fails listing the clusters).

do you have any localization version of vmware etc? did it ever worked with foreman?

VMWare Esxi 5.0.0 managed by VSphere (VMware vCenter Server 5.0.0.16964) First list of the BUG Desription :)
Cluster is named thuis. (dutch for home) My whole setup is running on wmware-workstation 9.0.2
Same setup does work with foreman 1.1

Foreman 1.1 uses fog-1.9.0. Foreman 1.2 tested with fog-1.8.0-3 (in rc1 yum repo an with 1.1.11-3)

Thanks for the log files, that's very useful.

Ronny M wrote:

I'm not an expert but it looks like it's fog related.

fog 1.9.0 installed with foreman 1.1-stable is able to list servers when using fog on linux prompt. (attachment: fog-1.9.0-foreman1.1-stable)
fog 11.1.1 installed with foreman 1.2 RC2 results in: (Object doesn't support #inspect) for same command to list servers. (attachment: fog-1.11.1-foreman1.2-RC2)

attached examples/logs for both situations.

Although it doesn't list servers it does see vmware templates. (Also in the foreman GUI: Provisioning => Compute resources => vmware => Virtual machines)

what is the version of rbvmomi gem? it looks like we might have the wrong version in 1.2 vs 1.1?

ruby193-rubygem-rbvmomi-1.2.3-7.el6.noarch

The above version is of foreman 1.2 RC2

foreman 1.1-stable has rubygem-rbvmomi-1.5.1-1.el6.noarch

So you might be right the one in 1.2 is older then the one in 1.1.

Ok, it will test it as soon as the new version is availible

I'm hitting the same issue using foreman 1.2 rc.2 and vmware ESXi, 5.1.0,914609. I have updated rbvmomi as above and can now se VM Settings/Details. But when creating a new VM i get.

Failed to create a compute vmware (VMWare) instance rhidm.example.com: failed to create vm: unexpected type Task (Task/Object/Foreman::Util/PSON::Pure::Generator::GeneratorMethods::Object/GettextI18nRails::HtmlSafeTranslations/FastGettext::Translation/PP::ObjectMixin/ActiveSupport::Dependencies::Loadable/JSON::Ext::Generator::GeneratorMethods::Object/Kernel/BasicObject)

Although not all of the following rpm's are installed in both foreman 1.1 and 1.2, the ones in foreman 1.2 are also older then the onces in foreman 1.1
Not sure if this is what causes the problems but expected newer rpm's in foreman 1.2

1. foreman 1.1:
   rubygem-ffi-1.0.11-1.el6.x86_64.rpm
   rubygem-json-1.6.8-1.el6.x86_64.rpm
   rubygem-net-ldap-0.3.1-1.el6.noarch.rpm
   rubygem-pg-0.13.2-2.el6.x86_64.rpm
   rubygem-rest-client-1.6.7-1.el6.noarch.rpm

1. foreman 1.2:
   ruby193-rubygem-ffi-1.0.9-10.el6.x86_64.rpm
   ruby193-rubygem-json-1.5.4-29.el6.x86_64.rpm
   ruby193-rubygem-net-ldap-0.2.2-5.el6.noarch.rpm
   ruby193-rubygem-pg-0.12.2-8.el6.x86_64.rpm
   ruby193-rubygem-rest-client-1.6.1-4.el6.noarch.rpm

Any plans to build newer versions for the 1.2 RC2 rpm's mentioned above?

I'm happily willing to test them as soon as they come available.

Any plans to build newer versions for the 1.2 RC2 rpm's mentioned above?

I'm happily willing to test them as soon as they come available.

I hadn't planned on building them as they don't look directly related. Amos is planning to look at this on an RPM build to see if he can reproduce it, if any of them look like likely suspects then we'll try some rebuilds.

I think this is due to a bug in rbvmomi 1.6.0, as I went and built the latest release when we found it was out of date above. I've applied a patch from upstream that was committed since the release and it seems to help on my local development setup, here's a test RPM build for you to try:

http://koji.katello.org/koji/getfile?taskID=39976&name=ruby193-rubygem-rbvmomi-1.6.0-2.git.18.e7f3436.el6.noarch.rpm

If that doesn't help, I could go back and build 1.5.1, but I'd like to avoid that as it means yum downgrades or epoch numbers.

My RHEL 6 instance is now getting the error "failed to create vm: undefined method `resourcePool' for nil:NilClass", so I'll look into this next.

Doesn't work for me either. With Folder on: "VM Folder" I get the following error on my first attempt to create a new VM after updating rvbcomi to 1.6.0-2.

Unable to save
Failed to create a compute vmware (VMWare) instance test300.local.domain: failed to create vm: undefined method `resourcePool' for nil:NilClass

But when I try to create another VM with different name and ip after above error occurred I get the following error again:

Unable to save
Failed to create a compute vmware (VMWare) instance test400.local.domain: failed to create vm: unexpected type Task (Task/Object/Foreman::Util/PSON::Pure::Generator::GeneratorMethods::Object/GettextI18nRails::HtmlSafeTranslations/FastGettext::Translation/PP::ObjectMixin/ActiveSupport::Dependencies::Loadable/JSON::Ext::Generator::GeneratorMethods::Object/Kernel/BasicObject)

But With Folder on: "vm/Servers" during a first attempt after updating the rpm I get the following error right away:

Unable to save
Failed to create a compute vmware (VMWare) instance hallo.local.domain: failed to create vm: unexpected type Task (Task/Object/Foreman::Util/PSON::Pure::Generator::GeneratorMethods::Object/GettextI18nRails::HtmlSafeTranslations/FastGettext::Translation/PP::ObjectMixin/ActiveSupport::Dependencies::Loadable/JSON::Ext::Generator::GeneratorMethods::Object/Kernel/BasicObject)

Dominic,

You are right.

I applied you pull request into my setup and know creating a VM does work :)

Ronny M wrote:

I applied you pull request into my setup and know creating a VM does work :)

Thank you for testing!

Ronny M wrote:

Dominic,

You are right.

I applied you pull request into my setup and now creating a VM does work :)

Oeps sorry,

Correcting a typo in my comment duplicated my comment :(