1. Overview
This guide explains how to identify and resolve common errors that may occur while creating a Virtual Machine (VM) on the Cloud platform.
2. Common Virtual Machine Creation Errors
2.1 No Available Public IPs
Cause
The selected region has no available public IP addresses.
Resolution
- Select a different region (for example, create the VM in West-3 instead of West-2).
- If a public IP is not required, create the VM using only a private IP address.
2.2 Insufficient Quota
Cause
The project has reached its allocated quota for resources such as CPU, RAM, storage volumes, or GPU.
Resolution
- Delete any unused Virtual Machines or storage volumes.
- If additional resources are required, request a quota increase from Cloud Support.
2.3 Network or Subnet Not Found
Cause
The selected network is incorrect, or the required network or subnet has been deleted.
Resolution
- Select the correct network and subnet during Virtual Machine creation.
- If the required network or subnet does not exist, create a new private network and subnet.
2.4 Volume Creation Failed
Cause
The storage backend encountered an error, or there is insufficient storage capacity.
Resolution
- Try creating the Virtual Machine again.
- Verify that the storage quota has not been exceeded.
- Create the volume manually and attach it to the Virtual Machine.
3. When to Contact Support
Contact Cloud Support if:
- The same error occurs in multiple regions.
- No public IP addresses are available in the selected region.
- There are issues related to images or flavors.
Provide the following information when contacting support:
- Screenshot of the error message.
- Region name.
- Virtual Machine flavor.
- Operating system image.
- Time when the error occurred.