Issue when creating cluster using IP range network

92 views
Skip to first unread message

JunChi ZHANG

unread,
Jul 8, 2013, 6:32:30 AM7/8/13
to serenge...@googlegroups.com
On 0.9 deployment, I'm trying to create a basic cluster by an IP range network which I configured manually, it returns error says: cluster test2 create failed: internal error: REST API transport layer error. 

Attaching serengeti log as well as snapshots of new portgroup in vc I used to map IP range network, as well as CLI command to add this IP ragne network to serengeti. 

I previously created a same cluster successfully using DHCP network, on the same deployment instance.

Appreciate your help.

Thanks,
Junchi


restapierror.zip

Jesse Hu

unread,
Aug 1, 2013, 11:10:38 PM8/1/13
to serenge...@googlegroups.com
Hi Junchi,

The log shows:

com.vmware.bdd.exception.ClusterConfigException: Some host in vc cluster defaultCluster does not have specified network ippool.
at com.vmware.bdd.exception.ClusterConfigException.NETWORK_UNACCESSIBLE(ClusterConfigException.java:111)
at com.vmware.bdd.manager.ClusterManager.validateNetworkAccessibility(ClusterManager.java:467)
at com.vmware.bdd.manager.ClusterManager.createCluster(ClusterManager.java:411)
at com.vmware.bdd.rest.RestResource.createCluster(RestResource.java:155)

If the portgroup specified by network ippool is newly added into vCenter, or some host is newly added to that portgroup, please try to restart vCenter and Serenget Tomcat service to let it take effect.

JunChi ZHANG

unread,
Aug 5, 2013, 2:28:17 AM8/5/13
to serenge...@googlegroups.com
Thanks Jesse, the log is clear. I was given an update by Emma about root cause of this issue that the network/portgroup newly added in VC, is not updated in Serengeti VC object cache.
The team had a bug to track, a fix will be included in the next release.
What a great news!

- Junchi
Reply all
Reply to author
Forward
0 new messages