Re: Serengeti .8 Cluster Create fails with "Do not give vc_clusters' info"

109 views
Skip to first unread message

Emma Lin

unread,
May 14, 2013, 9:40:30 PM5/14/13
to serenge...@googlegroups.com
nathan,
From the cluster spec file testHadoop.json file, in the "cloud_provider" section, there should have datastore and vc cluster/resource pool information. This error is because missing those information.
Generally, after Serengeti server is deployed under VC cluster/Resource Pool, the resource pool and data store, where Serengeti server located, will be added into Serengeti Meta DB, and that information will be passed to Cloud Manager, to put the deployed hadoop cluster.
You can check your system through CLI command "datastore list --detail" and "resourcepool list --detail".
For how to change those information, please check our user guide.

thanks
Emma

From: "Nathan Earixson" <eari...@gmail.com>
To: serenge...@googlegroups.com
Sent: Wednesday, May 15, 2013 12:31:59 AM
Subject: Serengeti .8 Cluster Create fails with "Do not give vc_clusters' info"

Hi,

We're running Serengeti 0.8 and trying to deploy our first Hadoop cluster.


Here's the relevant portion of the task stdout and I've attached all the logs I could think of.


Creating machines in Cloud
[2013-05-13 21:58:13 +0000] INFO: begin action:create
[2013-05-13 21:58:13 +0000] INFO: [CREATE]enter create_and_update...
CONFIG WARN: unknown config item: vc_clusters
[2013-05-13 21:58:13 +0000] ERROR: [CREATE]create failed with Do not give vc_clusters' info. /usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager/cloud.rb:175:in `create_cloud_provider'


The managemnt-server can see the Vcenter server and has discovered the right Datacenter. what else can I look at?

thanks,
-nathan

--
 
---
You received this message because you are subscribed to the Google Groups "serengeti-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serengeti-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

jun wang

unread,
May 15, 2013, 10:06:31 AM5/15/13
to serenge...@googlegroups.com
Also please have a look at /opt/Serengeti/logs/firstboot.stderr, and see if any error there that might prevent the information written into meta db.

Thanks,
Jun

jun wang

unread,
May 15, 2013, 10:24:16 PM5/15/13
to serenge...@googlegroups.com
Yes, serengeti does not support white spaces for cluster names. Here is the latest serengeti user guide at http://serengeti.cloudfoundry.com/pdf/Serengeti%20User%20Guide_0.8.pdf

That might help your deployment.


Date: Wed, 15 May 2013 15:21:42 -0700
From: eari...@gmail.com
To: serenge...@googlegroups.com
Subject: Re: Serengeti .8 Cluster Create fails with "Do not give vc_clusters' info"

Thanks all. It looks like our problem is that most of our Cluster names have spaces in them. Serengeti does not appear to like this, whether or not I escape the space or quote the string:

resourcepool add --name testSerengeti --vccluster "Test 5.1i" --vcrp testSerengeti



I am going to try to deploy serengeti on another cluster and make the Windows admins rename the clusters to NOT USE spaces!


-n

Nathan Earixson

unread,
May 22, 2013, 12:21:02 PM5/22/13
to serenge...@googlegroups.com
Just  a note -- after renaming our vSphere Clusters more sensibly I was able to deploy a Hadoop cluster fairly easily.

thanks all,

-n

Sean

unread,
Aug 12, 2013, 2:30:52 PM8/12/13
to serenge...@googlegroups.com
I'm getting the exact same error message but I don't think mine has anything to do with naming. I have a very generic setup that i controll. I'm not sure what a vc_cluster is or what it means to create machines in cloud. 


Here is the log from /opt/serengeti/log/task/1/stdout.log
Creating machines in Cloud
[2013-08-12 15:54:57 +0000] INFO: begin action:create
[2013-08-12 15:54:57 +0000] INFO: [CREATE]enter create_and_update...
CONFIG WARN: unknown config item: vc_clusters
[2013-08-12 15:54:57 +0000] ERROR: [CREATE]create failed with Do not give vc_clusters' info. /usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager/cloud.rb:175:in `create_cloud_provider'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager/cloud_create.rb:36:in `block in create'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager/cloud.rb:353:in `action_process'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager/cloud_create.rb:34:in `create'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager/iaas_task.rb:82:in `create'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager.rb:105:in `block in create_cluster'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager.rb:70:in `call'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager.rb:70:in `call_op'
/usr/lib/ruby/gems/1.9.1/gems/cloud-manager-0.8.0/lib/cloud_manager.rb:87:in `block in op_helper'
Reply all
Reply to author
Forward
0 new messages