Translations:Cloud troubleshooting guide/12/en

1. First check to see if launching a VM would exceed some resource limit (also known as a "quota"). Your cloud project has a limit on the number of VMs, CPUs, and GBs of RAM you can have in use at any given time. If you try to launch a VM that would cause you to exceed any of these limits, the launch will fail. To check your limits, log in to your project cloud dashboard (see Cloud for a list of login links) and on the left-side navigation menu click "Compute", then "Overview". It will show you how much of your allotted resources are currently in use. If you need more resources for your project, request them using this form. More details about resource limits and how to obtain large resource allocations (>10TB) can be found at Cloud RAS Allocations.
2. If you get the message Error: Failed to perform requested operation on instance "...", the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available.] then check the following:
   1. You may have chosen an inappropriate Availability Zone when trying to launch the instance. The first section you fill in when launching an instance is the "Details" section which includes Instance Name, Description, and Availability Zone. The default setting is "Any Availability Zone" which allows OpenStack to choose a zone for you. If you manually select the zone yourself instead of using the default option you may see this "not enough hosts" error. Fix this by setting the Availability Zone back to "Any Availability Zone".
   2. If you still get this "not enough hosts" error, or there is some reason why you need a particular availability zone, send an email to cloud@tech.alliancecan.ca and provide the cloud name, project name, the steps you have taken thus far, and the reason why you need a particular availability zone if that is the case.
3. If you have followed these steps and still can’t get your instance to boot, submit a ticket to cloud@tech.alliancecan.ca with your username, project name, cloud name, and any information you collected during troubleshooting.