You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Chip Childers (JIRA)" <ji...@apache.org> on 2013/02/05 21:25:13 UTC
[jira] [Commented] (CLOUDSTACK-1165) VMware resource manager not
found
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571698#comment-13571698 ]
Chip Childers commented on CLOUDSTACK-1165:
-------------------------------------------
Did you build as non-oss with the VMware jars?
> VMware resource manager not found
> ---------------------------------
>
> Key: CLOUDSTACK-1165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1165
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Centos 6.3, vmware
> Reporter: Venkata Siva Vijayendra Bhamidipati
>
> When creating a vmware cluster, the mgmt server fails with this message:
> INFO [cloud.api.ApiServer] (1719136796@qtp-119090941-4:) Could not find corresponding resource manager for VMware
> The corresponding vmops.log excerpt is pasted below:
> 2013-02-05 11:36:31,187 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-10) Executing org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd for job-10
> 2013-02-05 11:36:31,230 DEBUG [cloud.network.NetworkServiceImpl] (Job-Executor-10:job-10) ISOLATION METHODS:[VLAN]
> 2013-02-05 11:36:31,238 DEBUG [cloud.network.NetworkServiceImpl] (Job-Executor-10:job-10) Deleting existing vnet range for the physicalNetwork id= 200 and zone id=1 as a part of updatePhysicalNetwork call
> 2013-02-05 11:36:31,239 DEBUG [cloud.network.NetworkServiceImpl] (Job-Executor-10:job-10) Adding vnet range 2410-2430 for the physicalNetwork id= 200 and zone id=1 as a part of updatePhysicalNetwork call
> 2013-02-05 11:36:31,377 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-10) Complete async job-10, jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.response.PhysicalNetworkResponse@55c70eac
> 2013-02-05 11:36:31,411 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-10:job-10) Done executing org.apache.cloudstack.api.command.admin.network.UpdatePhysicalNetworkCmd for job-10
> 2013-02-05 11:36:34,191 DEBUG [cloud.api.ApiServlet] (1719136796@qtp-119090941-4:null) ===START=== 10.217.252.50 -- GET command=queryAsyncJobResult&jobid=d6d4b60a-5b95-4e70-a4ee-9654d8116a45&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994083
> 2013-02-05 11:36:34,228 DEBUG [cloud.async.AsyncJobManagerImpl] (1719136796@qtp-119090941-4:null) Async job-10 completed
> 2013-02-05 11:36:34,236 DEBUG [cloud.api.ApiServlet] (1719136796@qtp-119090941-4:null) ===END=== 10.217.252.50 -- GET command=queryAsyncJobResult&jobid=d6d4b60a-5b95-4e70-a4ee-9654d8116a45&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994083
> 2013-02-05 11:36:34,243 DEBUG [cloud.api.ApiServlet] (1719136796@qtp-119090941-4:null) ===START=== 10.217.252.50 -- GET command=addCluster&zoneId=d7a58f91-34f1-4727-843f-730120b15224&hypervisor=VMware&clustertype=ExternalManaged&podId=aa86996d-21e4-467b-81c8-a3bdedffe932&username=Administrator&url=http%3A%2F%2F10.223.52.61%2Fvijay-dc%2Fcluster1&clustername=10.223.52.61%2Fvijay-dc%2Fcluster1&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994135
> 2013-02-05 11:36:34,330 INFO [cloud.api.ApiServer] (1719136796@qtp-119090941-4:null) Could not find corresponding resource manager for VMware
> 2013-02-05 11:36:34,332 DEBUG [cloud.api.ApiServlet] (1719136796@qtp-119090941-4:null) ===END=== 10.217.252.50 -- GET command=addCluster&zoneId=d7a58f91-34f1-4727-843f-730120b15224&hypervisor=VMware&clustertype=ExternalManaged&podId=aa86996d-21e4-467b-81c8-a3bdedffe932&username=Administrator&url=http%3A%2F%2F10.223.52.61%2Fvijay-dc%2Fcluster1&clustername=10.223.52.61%2Fvijay-dc%2Fcluster1&response=json&sessionkey=w7y8aGapGgsNK4wDAirE7QC2GBc%3D&_=1360092994135
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira