Post

2 followers Follow
0
Avatar

Import Datastore fails

Hi!

 

I'm currently trying to get vOneCloud 2.0 installed and configured. Everything works fine but importing datastores. When I try to import them I receive the following error messaage:

undefined method `key' for nil:NilClass

I tried the webgui and command line, same error.

 

Any Ideas?

 

THX, Oliver.

Oliver Lewa

Please sign in to leave a comment.

5 comments

0
Avatar

It seems you are hitting a bug when a DS is not associated with a host. Let's try and nail down the issue.

Could you please log into the appliance:

 http://docs.vonecloud.com/2.0/simple_cloud_deployment/download_and_deploy.html#login-to-the-appliance

and replace file /usr/lib/one/ruby/vcenter_driver.rb with the following file:

 https://gist.github.com/anonymous/089b8f6c1c139b2ec35e345520159634

and try again? Please let us know about the outcome.

vOneCloud Support Team 0 votes
Comment actions Permalink
0
Avatar

Hi!

 

Thanks for the quick reply.

I replaced the vcenter_driver.rb as you requested it and tried again to import vCenter Datastores. Using the web gui, the error remains the same, using command line i'm asked if I want to process the only Datacenter avaible but the result is: no new datastores found in ...

Thanks, Oliver.

Oliver Lewa 0 votes
Comment actions Permalink
0
Avatar

We forgot to mention that you should restart OpenNebula through the control panel to get the web ui to acknowledge the change

Does the vCenter cluster have any ESX host associated? If so, does any of this ESX have a mounted datastore?

vOneCloud Support Team 0 votes
Comment actions Permalink
0
Avatar

Hi!

 

I restarted OpenNebula and now I'm getting the same message "No new Datastores found" in Web UI. The vCenter I try to connect has a Datacenter, Clusters, Hosts and Datastores and it has one active DS with no Host assinged, however this happened.

 

THX Oliver.

Oliver Lewa 0 votes
Comment actions Permalink
0
Avatar

one active DS with no Host assinged, however this happened.

This is most likely the cause, a DS needs to be associated with a ESX part of a cluster imported in vOneCloud for the import to work.

 

vOneCloud Support Team 0 votes
Comment actions Permalink