Cloud troubleshooting guide: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 56: Line 56:
<li>Now check to see if there is a snapshot of the volume: If there are snapshots of the volume you are trying to delete, you must delete the snapshots first, then you can delete the source volume. To check if your volume has snapshots, open the “Volumes” menu on the left side panel, and then select “Snapshots”. You will see a list of all your snapshots. Look at the volume name column, to see if there are any snapshots of the volume you wish to delete. To delete a snapshot click the drop-down arrow in the “Actions” column in the row for the snapshot you wish to delete and select “Delete Volume Snapshot”.</li>
<li>Now check to see if there is a snapshot of the volume: If there are snapshots of the volume you are trying to delete, you must delete the snapshots first, then you can delete the source volume. To check if your volume has snapshots, open the “Volumes” menu on the left side panel, and then select “Snapshots”. You will see a list of all your snapshots. Look at the volume name column, to see if there are any snapshots of the volume you wish to delete. To delete a snapshot click the drop-down arrow in the “Actions” column in the row for the snapshot you wish to delete and select “Delete Volume Snapshot”.</li>
<li>If you have followed these steps and still can’t delete your volume it's time to submit a ticket. Email cloud@computecanada.ca with any info collected during troubleshooting, username, project name cloud name and volume UUID.  
<li>If you have followed these steps and still can’t delete your volume it's time to submit a ticket. Email cloud@computecanada.ca with any info collected during troubleshooting, username, project name cloud name and volume UUID.  
<li>More information for contacting support and ticket submission best practices etc. can be found on the [[Technical support/en|Compute Canada Technical Support page]].</li></ol>
==Issue: My virtual machine won't launch==
<ol><li>First check to see if your virtual machine (VM, also known as "instance") is over quota: Your cloud project has a limit on the number of VM’s, CPUS and GB of RAM you can have in use at any given time. If you try to launch a VM that would cause you to exceed your project quota (whether it’s due to number of VM’s, CPUS or RAM), then your VM launch will fail. You can check your project quota by logging into your project cloud dashboard (see the [[Cloud/en|cloud wiki page]] for a list of cloud login links) and using the left side navigation menu, and selecting 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 you can request them using [https://docs.google.com/forms/d/e/1FAIpQLSeU_BoRk5cEz3AvVLf3e9yZJq-OvcFCQ-mg7p4AWXmUkd5rTw/viewform this request form]. Details for resource request limits and how to obtain large resource allocations (>10TB) can be found at the [[Cloud RAS Allocations/en|Cloud RAS Allocations wiki page]].</li>
<li>If you are getting the following error: "Error: Failed to perform requested operation on instance "instance_name", 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:
<ol><li>You may be choosing an inappropriate availability zone when you are launching your instance. The first section you need to fill in when launching your instance is the “Details” section which includes your instance name (name for your virtual machine), the description, and the Availability Zone. The default setting is “Any Availability Zone” which allows the software to choose a Zone based on your requirements and the system availability. If you manually select the zone yourself instead of using the default option you may see this “not enough hosts” error. You can fix this by setting your availability zone back to “Any Availability Zone”.</li>
<li>If you are still getting this “not enough hosts error” or you have extenuating reasons why you need a particular availability zone, send an email to cloud@computecanada.ca and provide the cloud name, project name, all the steps you have taken to troubleshoot thus far, and the extenuating reasons why you need a particular availability zone if that is the case.</li></ol>
<li> If you have followed these steps and still can’t get your instance to boot it's time to submit a ticket. Email cloud@computecanada.ca with any info collected during troubleshooting, username, project name cloud name.</li>
<li>More information for contacting support and ticket submission best practices etc. can be found on the [[Technical support/en|Compute Canada Technical Support page]].</li></ol>
<li>More information for contacting support and ticket submission best practices etc. can be found on the [[Technical support/en|Compute Canada Technical Support page]].</li></ol>
cc_staff
169

edits