When attempting to deploy a system, the following error message may appear: "Sorry, you don't have access to any cloudspaces that can run this deployment." The reasons for receiving this message are listed below.
Wrong Project Selected
- If the wrong Project is selected, you may not be able to launch your Deployment.
- Your default project is set to "Community" upon account creation, so you will have to change your default project. Also, make sure to select the Project associated with the Cloudspace you are deploying into. Select the "Project" drop down menu in the top-right corner of the page.
System Specification may not be supported in the Cloudspace
Your Deployment contains 1 or more system(s) defined by one of the following specifications:
- Operating System
- Number of CPUs
- Memory / RAM
- Number of Network Interfaces
- Remote Access Capability
One or more System(s) in your Deployment may not include an OS Template that meets your system specification.
Contact your Cloudspace Admin to check what Operating Systems are available inside your Cloudspace and adjust your System Specifications accordingly.
If you are a Cloudspace Admin
- From the Deployment click on the Scenario in the "From Scenario" link.
- Select each System from the Scenario to inspect the specifications and verify the following:
Ensure the selected Operating System exists in the Cloudspace
- From the Main Nav Menu, select Cloudspaces
- Select your Cloudspace
- Click on the Operating System Templates Tab
- Ensure the Selected Operating System exists
Ensure the Operating System Template meets the System Specifications
Click the Edit button on the OS Template, and ensure the System Specifications do not exceed the following:
- Maximum CPU Count
- Maximum Memory
- Boot Disk Size
- Maximum Network Interfaces -- Click here for additional info on Maximum Network Interfaces on AWS EC2 and Openstack
- Remote Access -- If the System Specification requires remote access, then the OS Template must have SSH, VNC, or RDP configured
Update the OS Template settings as appropriate and ask the user to re-try the Deployment.
If none of the above solve the problem, please submit a Support Request