Issue:
Deployments fail.
History shows the placement error message:
Create - Failed
No placement exists that satisfies all of the request requirements. See if suitable placements and cloud zones exist for the current project and they have been properly tagged.
Verified vCenter is up-and-running.
Verified that storage and compute are available.
Also, confirmed IPs are available, although that would deliver a different message later in the allocation.
Resolution:
Check the cloud zone and also the cloud accounts for an error.
Checking Cloud Zone:
vRA/vRO 8 appliance --> Login --> Assembler --> Configure (left menu twistie) --> Cloud Zones (left menu view option) --> filter to the name of the zone with the issue --> Click Open to view the cloud zone --> Compute (tab)
Confirm the compute tags are present, and no issues are visible.
Check the Cloud Account:
vRA/vRO 8 appliance --> Login --> Assembler --> Connections (left menu twistie) --> Cloud Accounts (left menu view option) --> filter to the name of the zone with the issue --> Click Open to view the cloud account --> Status (heading area)
Check for warning or caution messages. They may include:
- Data collection failed. See details ...
- Image synchronization failed. See details ...
- Unable for deployment. [UPDATE]
For the top two, you can click the See details text link.
For the lower one, you can click the UPDATE button to try again.
In this case, above the Status heading, the cloud account showed the following error for the target cloud zone. This error was causing the Unable for deployment text to be displayed.
Failed to validate credentials. Error: The connection with the vAPI endpoint can not be established. Please make sure the vAPI endpoint is running in the vCenter (com.vmware.vapi.endpoint.failedToLoginMaxUserSessionCountReached User session count is limited to 500. Existing session count is 500 for user loginaccount@local )
To reset the stale/non-used sessions, we restarted vCenter to clear the error.
previous page
|