Troubleshooting
Problem
Attempts to create a project on VMWare results in the error "CTJZH8330E - The cloud management subsystem was unable to create any of the requested servers".
Symptom
The following errors are issued in the Console Log:
CTJZH8319E - Service request 1015 was closed due to errors during processing. Project test56 may not be operational
CTJZH8317I - BlueCloud processing has finished for project /cloud/rest/projects/1002/ with failures returning status 3
CTJZH8330E - The cloud management subsystem was unable to create any of the requested servers.
CTJZH3405E - Workflow PMRDPRBSYP failed
CTJZH0074I - Cancel actual and all remaining tasks of the management plan
CTJZH3411I - Management Plan Create Project completed
Cause
From the log analysis, the root cause of the problem is failure of workflow:
VMware_VI3_Cluster_CreatePortGroup
<deployment-request id="15223" error-details="VMware_VI3_Cluster_CreatePortGrou(line:117)
VMware_VI3_Host_Add_VLAN(line:86)
AddVLAN(line:30)
RP$CreateVirtualServer(line:310)
RP$ClusterProvision(line:92)com.thinkdynamics.kanaha.de.DeploymentException: COPDEX041E An unexpected deployment error occurred
The communication between virtual center and its agents on the ESX fails.
Starting from TSAM 7.2.2.x there are new features in VMware port group handling (such as support for virtual distributed switches).
In this case the port group management is delegated to the Virtual Center. The virtual center is then responsible for doing the port group management on the ESX hosts which are in the cluster and using the same distributed switch.
If you use the port groups on standard switches, the communication capabilities from TSAM to the ESX for the port group manipulation is still required.
As long as the connectivity between the TSAM node, virtual center and the ESX hosts in the cluster does not work reliable you will get these provisioning problems.
Diagnosing The Problem
Steps to troubleshoot:
- Look in the virtual center client and check which ESX servers are member of the cluster in VWware.
TSAM will try to create the new port group on the virtual switch for each of the ESX in cluster.
If the virtual center client shows one of the ESX in the Cluster as not active / available a provisioning request will fail if a new port group has to be generated.
- Ping each of the ESX servers and the virtual center from the TSAM node.
If the checks are fine then a provisioning should work.
Connectivity required from network standpoint: - TSAM to virtual center
- TSAM to ESX hosts in cluster
- Virtual Center to managed ESX hosts
Resolving The Problem
If the virtual center client shows one of the ESX in the Cluster as not active, make it available to allow the provisioning request to succeed when a new port group is generated.
If the pings to the ESX servers from the TSAM node fails, identify the source of the network issue and resolve.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21599283