Cloud troubleshooting guide: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 48: Line 48:
<li>Check that your ip address is unblocked for SSH connections to your VM. You can do this by clicking on “Network” in the left-hand side navigation panel, then “Security groups”. Click “Manage Rules for the security group for your VM (unless you have setup a separate group for your VM, this will be the “default group”. You can check this by going to the instance overview page). There should be a TCP rule there to allow ingress ssh at your-ip-address/32. If this rule is not there click add rule, select SSH from the list, then enter your-ip-adress/32 in the CIDR field box at the bottom and click “Add”.</li></ol></ol>
<li>Check that your ip address is unblocked for SSH connections to your VM. You can do this by clicking on “Network” in the left-hand side navigation panel, then “Security groups”. Click “Manage Rules for the security group for your VM (unless you have setup a separate group for your VM, this will be the “default group”. You can check this by going to the instance overview page). There should be a TCP rule there to allow ingress ssh at your-ip-address/32. If this rule is not there click add rule, select SSH from the list, then enter your-ip-adress/32 in the CIDR field box at the bottom and click “Add”.</li></ol></ol>
<li>If you have completed all these steps and still cannot connect to your instance, it’s time to submit a ticket. Send an email to cloud@computecanada.ca and provide the cloud name, project name, instance UUID (you can find this by clicking on Instances -in the compute menu on the left hand side- then clicking on the specific instance name you are having trouble with, then look at the ID field in the overview tab for that instance. The UUID will be a long alpha-numeric sequence) , and all information collected from the above steps.</li>
<li>If you have completed all these steps and still cannot connect to your instance, it’s time to submit a ticket. Send an email to cloud@computecanada.ca and provide the cloud name, project name, instance UUID (you can find this by clicking on Instances -in the compute menu on the left hand side- then clicking on the specific instance name you are having trouble with, then look at the ID field in the overview tab for that instance. The UUID will be a long alpha-numeric sequence) , and all information collected from the above steps.</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>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: I can't delete my volume==
<ol>
<li>Check to see if the volume you are trying to delete is attached to a running virtual machine (VM, also known as instance): Volumes that are attached to running VM’s cannot be deleted. You can check this by logging into the cloud dashboard for your project (see the [[Cloud/en|cloud wiki page]] for a list of the cloud login links), opening the volumes menu on the left side navigation menu, then selecting volumes. You will be presented with a list of all your volumes. If the “attached to” column is empty then your volume is not attached. If there is a VM listed there, it is attached to that VM and will need to be detached before it can be deleted. For instructions on how to detach a volume see the “Detaching a Volume” section of the [[OpenStack/en|OpenStack Wiki page]].</li>
<li>Once you have the volume detached check the status of your volume: open the Volumes menu on the left hand side and select "Volumes" from the menu. Now look at the "Status" column for your volume. If it is still listed as "In-use" then you need to submit a ticket: Email cloud@computecanada.ca with any info collected during troubleshooting, username, project name cloud name and volume UUID. If it is listed as "available" proceed to the next step.</li>
cc_staff
169

edits