Skip to content

Known Issues

This page is for a list of Known Issues that may appear when managing or working with OpenCloud.

Key for status's used to delineate which known issues have been fully resolved and deployed

indicates an issue is active and a fix is not yet fully deployed.

indicates that a fix has been fully deployed.

OpenCloud

vTPM Support

vTPM is now supported and can be added to an Instance via Instance Settings. See Adding Settings for instructions.

Creating Network - Basic - Self-Provisioned causes instances to deploy in an error state

Issue

  • Creating this network and only specifying IPv4 Gateway and IPv4 Netmask shows that the network created successfully, however, when you try and deploy instances on it they go into an error state.

Workaround

  • Specify a IPv4 start IP and IPv4 end IP when creating the network.
Uploaded Volume fails to attach

Issue

  • This issue only occurs when the following conditions are met
    • Upload a Volume from local disk
    • Volume is in an uploaded state
    • Instance has no Volumes attached
  • When all items above are true, the instance will fail to attach and you will receive an error that the volume is not allocated or ready.

Workaround

  1. Create a temporary instance that has a volume attached.
  2. Attach the uploaded volume and wait a few minutes.
  3. Un-attach the volume from the temporary instance
  4. Attach it to the instance with no volumes attached.
Request Failed: API listProjects does not exist

Issue

  • When performing certain actions such as assigning an instance to another account, an error occurs such as "Request failed. (432) The API [listProjects] does not exist or is not available for the account Account".

Workaround

  • None at this time. This error can be ignored and is informational only.
Windows instances do not show metrics for memory correctly

Issue

  • When viewing metrics on Windows instances it shows 100% memory used.

Workaround

  • None at this time. This will be resolved in a future update.
Adding More than 1 Disk to Powered on Instances fails

Issue

  • When an instance is powered on and you try to add more than 1 disk, you receive an error. Failed to attach volume test to VM <Instance Name>; org.libvirt.LibvirtException: internal error: No more available PCI slots

Workarounds

  • Power off the instance to add multiple disks.
  • Start and Stopping the instance will reset the counter to allow 1 more disk to be added when powered on.