VMmanager Knowledge Base
en En
es Es

Errors list

Error codeInterface messageBrief descriptionPossible solutions

0

Unknown Error

An error has occurred that cannot be determined by the platform.

Study the logs of the service that was accessed when the error occurred. Contact the technical support.

401You are not authorized, or your session has expired, please try to re-authenticateUser is not authorized.Repeat the authorization procedure.
403Not enough rights to perform the requestThe user lacks rights to perform the request.Contact your program administrator.
404The page you requested was not foundRequest for a non-existent interface page.Return to the previous page using browser tools.
501An internal server error has occurredInternal server error.Repeat the request.
503Service temporarily unavailable. Please try sending the request again laterProblem with service operation.Repeat the request.
504Service is not responding. Please try sending the request laterProblem with service operation.Repeat the request.

1003

A socket descriptor is in use

Error of the gomon monitoring service on the cluster node. 

Restart the gomon service on the cluster nodes.

1111

Unexpected Error

An error has occurred that cannot be detected by the platform.

Study the logs of the service that was accessed when the error occurred. Contact the technical support.

1352

Platform movement already in progress

The platform migration to the virtual machine is already running.

Wait for the platform to be migrated to the virtual machine. 

1354

Platform not moved to VM: Supported OS is not available in the selected cluster

Failed to move the platform to the VM. There is no suitable OS template in the selected cluster.

  • In the cluster settings, add the OS that matches the OS on the platform server.
  • If you use your own OS templates, make sure that their names meet the conditions given in the article Moving platform to VM.

3001

Unauthorized

The request was executed without authorization.

Make sure that the request is executed under the authorized user name.

3003

User not found

User not found. 

Select an existing user.

3004

Template not found

The requested OS template is missing.

Select an existing OS template.

3005Access denied

The user does not have permission to perform the operation.

  • Check account access settings.
  • If the error occurs when attempting to delete a user, verify that the request is from the Administrator role.
  • If an error occurs when attempting to create a VM with SPICE access, verify that the request is from the Administrator or Advanced user role.

3008

Bad request

Error in forming or processing a request.

If the request is executed via API, check the format of the request. 

3009

Forbidden

No permissions to execute the request.

Check the permission level of the user executing the request.

3021

Error response from telegram-srv: Bad request: chat not found

No Telegram chat found to send notification.

Check the notification settings for Telegram. Add chat for notifications if necessary.

3023Invalid Telegram chat_idMissing or invalid Telegram chat id passed.Verify the chat_id passed in the parameters.
5006IP address unknownA non-existent IP address is specified.Specify an existing IP address.
5007Cluster id unknownA non-existent cluster is specified.Specify an existing cluster.
5008Mac id unknownA non-existent MAC address is specified.Specify an existing MAC address.
5009Network id unknownA non-existent network is specified.Specify an existing network.

5010

Os id unknown

API request contains the id of the operating system, information about which is not in the platform database.

Check if the operating system with this id is contained in the platform database.
5011Repository id unknownA non-existent repository is specified.Specify an existing repository.
5012Disk id unknownA non-existent disk is specified.Specify an existing disk.
5014Can not find proper task table recordUnable to find a suitable task in the task table.Clarify search conditions and repeat the task search.
5016Recipe id unknownA non-existent script for a VM is specified.Specify an existing script.
5017Preset id unknownA non-existent configuration is specified.Specify an existing configuration.
5018Network storage unknownA non-existent network storage is specified.Specify an existing network storage.
5019Storage tag unknownA non-existent storage tag is specified.Specify an existing storage tag.
5020Storage unknownA non-existent local storage is specified.Specify an existing local storage.
5021Host id unknownA non-existent VM is specified.Specify an existing VM.
5022Account id unknownA non-existent account is specified.Specify an existing account.
5023Image id unknownA non-existent image is specified.Specify an existing image.
5024Ip pool id unknownA non-existent IP address pool is specified.Specify an existing IP address pool.
5025Node id unknownA non-existent cluster node is specified.Specify an existing cluster node.
5026Ssh key id unknownA non-existent SSH key is specified.Specify an existing SSH key.
5027Os Group unknownA non-existent OS family is specified.Specify an existing OS family.
5028Hetzner ip id unknownA non-existent IP address in a cluster with the "Routing" setting type is specified.Specify an existing IP address.
5029Hetzner subnet id unknownA non-existent IP address subnet in a cluster with the "Routing" setting type is specified.Specify an existing subnet.
5030Virt pool id unknownA non-existent IP address pool is specified.Specify an existing pool.
5031Inconsistent params of ippools connectIncorrect IP address pool parameters.Check pool parameters.
5032Bad interface indexIncorrect network interface index.Check the network interface index.
5033Different number of interfacesThe number of network interfaces differs from the required number.Check the number of network interfaces.
5034Must set interfacesIncorrect network interface parameters.Check network interface parameters.
5035Too many interfacesThe number of network interfaces exceeds the maximum allowed.Reduce the number of network interfaces.
5036Two interfaces no support ipv6This configuration does not support IPv6 addressing.Change the configuration or switch the addressing type to IPv4.
5037Host interface unknownA non-existent VM interface is specified.Specify an existing VM interface.
5038Node script unknownIncorrect script specified for execution on the node.Specify correct values in the request.
5039Backup location unknownA non-existent VM backup storage is specified.Specify an existing storage.
5040Schedule unknownA non-existent VM backup schedule is specified.Specify an existing schedule.
5041Platform backup schedule unknownA non-existent platform backup schedule is specified.Specify an existing schedule.
5042Platform backup storage unknownA non-existent platform backup storage is specified.Specify an existing storage.
5043Platform backup unknownA non-existent platform backup is specified.Specify an existing copy.
5046Storage to cluster unknownA non-existent cluster storage is specified.Specify an existing storage.
5047Storage unknownA non-existent storage is specified.Specify an existing storage.
5048Script variable unknownA non-existent script variable is specified.Specify an existing script variable.
5049Recipe param unknownA non-existent script parameter is specified.Specify an existing script parameter.
5050Ip network id unknownA non-existent physical network is specified.Specify an existing network.
5052Host interface id unknownA non-existent VM interface is specified.Specify an existing VM interface.
5053Node interface id unknownA non-existent virtualization node interface is specified.Specify an existing virtualization node interface.
5054Node bridge id unknownA non-existent bridge is specified.Specify an existing bridge.
5055Node bond id unknownA non-existent bond is specified.Specify an existing bond.
5056Ip pool to cluster unknownA non-existent IP address pool in the cluster is specified.Specify an existing pool.
5057Vxlan id unknownA non-existent VxLAN is specified.Specify an existing VxLAN.
5058Can not find allocated ip in ipmgrIP address not found.Check the correctness of the IP address.
5059Disk bus is unknownA non-existent disk connection type is specified.Specify an existing connection type.
5060IP address unknownA non-existent IP address is specified.Specify an existing IP address.
5061Disk backup unknownA non-existent disk backup is specified.Specify an existing copy.
5063Snapshot id unknownA non-existent VM snapshot is specified.Specify an existing VM snapshot.
5064Tag id unknownA non-existent tag is specified.Specify an existing tag.
5065Preset disk id unknownA non-existent disk configuration is specified.Specify an existing configuration.
5068Snapshots not supportedSnapshot creation is supported only in clusters with KVM virtualization and one of the following storage types: file, local LVM, network LVM, NAS.Choose a supported virtualization or storage type.
5070Snapshot limit exceededVM snapshot limit exceeded.Delete unnecessary snapshots or increase the limit in the VM settings ("VM Snapshots" section).
5071Snapshot with RAM is forbiddenCreating snapshots with RAM state is forbidden for this VM.Allow saving RAM state in the VM settings ("VM Snapshots" section).

5072

Live migration is not available for VMs with Qcow2 format disk snapshots

The live migration of VMs with Qcow2 snapshots is not available.

  • Stop the VM before migration.
  • Delete VM snapshots before migration.
5073Live migration of VMs with network LVM snapshots is not allowedLive migration of VMs with snapshots in network LVM storage is not available.Stop the VM or delete snapshots before migration.
5075Migration of VMs with snapshots and storage type change is not allowedStorage type change during migration of VMs with snapshots is not supported.Delete snapshots or choose another node for migration.
5076Migration of VMs with LVM snapshots is not allowedMigration of VMs with snapshots in LVM storage is not supported.Delete snapshots before migration.
5077Host configuration change is forbidden for hosts with snapshotsVM configuration change is not supported for VMs with snapshots.Delete snapshots before changing the configuration.
5078Wrong snapshot typeIncorrect snapshot type.Contact support.
5083Migration of disks attached to VMs with LVM snapshots is not allowedMigration of VM disks with snapshots in local and network LVM storage is not supported.Delete snapshots before migration.
5084Migration of disks, attached to VMs with snapshots and storage type change is not allowedStorage type change during migration of VM disks with snapshots is not supported.Delete snapshots before migration.
5085Selected IP pool cannot be used on this type of host network interfaceThe selected IP pool does not match the type of the host network interface. For example, the interface belongs to the main network, but the pool is bound to an additional one.Choose a suitable pool.
5086Provided MAC address is already assigned to another host interfaceA record exists in the database to which the specified MAC address is bound.Specify a free MAC address.
5087Another interface of the host is already providing connection to the selected VxLANThe error occurs when, while creating a new interface, the user tries to bind it to a VXLAN segment that is already connected by another interface on the same VM.Choose another VXLAN or delete the old interface.
5094Cannot use DHCP while VM has the anti-spoofing option turned onDHCP is enabled in the request parameters and anti-spoofing is enabled on the VM.Disable anti-spoofing.
5095Cannot change node bridge as it belongs to different type of networkSwitching a VM's network interface to a bridge of a different network type (e.g., from main to additional) is not supported.Choose a bridge of the same network type.
5096Cannot allocate IP address on host interface which has DHCP turned onManual IP address allocation for interfaces with DHCP is not supported.Disable DHCP for the interface.
5100Some IP addresses are occupied by a blockSelected IP addresses intersect with an existing block.Change the range of selected IP addresses.
5101Network intersects with an existing oneThe settings of the network being created intersect with the settings of an existing one.Change the settings of the network being created.
5102IP address is busyIP address is busy.Select another IP address.
5103Network cannot be deleted. There is a dependent IPThe network cannot be deleted because there are dependent IP addresses.Identify dependent IP addresses and release them. Repeat network deletion.
5104Invalid IPAccess to an incorrect IP address.Check IP address settings.
5105Invalid IP rangeAccess to an incorrect IP address range.Check the IP address range settings.
5106Node cannot be deleted. There is a dependent hostThe virtualization node cannot be deleted because VMs are located on it.Delete VMs from the virtualization node, repeat node deletion.
5107Cluster cannot be deleted. There is a dependent nodeThe cluster cannot be deleted, there are dependent nodes.Delete dependent virtualization nodes, repeat cluster deletion.
5108Node cannot be deleted. There is a dependent diskThe node cannot be deleted, because there is a dependent disk.Delete the dependent disk.
5112Not enough rights on objectInsufficient rights to access the object.
  • Check object access rights.
  • If the error occurs during an API call, check if the object ID is specified correctly.
  • Perform the action under a user with the Administrator role.
5113There is no node in clusterThe cluster does not contain any nodes.Add a virtualization node to the cluster.
5114Cluster with same name already existsA cluster with the specified name already exists.Select a different name for the cluster.

5117

The VM is blocked

The error can occur if the administrator stopped the user's VM and then the VM was started by non-platform means. 

  • For users: contact the platform administrator.
  • For administrators: enable the VM using the platform means.
5120Bad URLInvalid URL.Check the URL input for correctness.
5121Source param missedA parameter for creating a VM is missing, no OS or image.Check the specified parameters for correctness.
5123Cluster cannot be selected automaticallyThe cluster cannot be selected automatically.Select the cluster manually.
5124OS not available on clusterOS is not available on the current cluster.Select a different OS or a different cluster.
5125Node check failedNode cluster check failed.Check the node server status.
5126Host creation blocked on nodeVM creation on the node is blocked.Allow VM creation on the node.
5127Can't find source locationFailed to find the node containing the image.Check the availability of the required image on the nodes.
5128Node is not readyNode is not ready for operation.Check node operability.
5129Image is not availableImage is unavailable.Check the image status.
5130Invalid time zoneInvalid time zone.Change the time zone.
5131OS not available on nodeOS is not available on the node.Check the availability of the required OS on the node.
5132Account cannot be deleted. There is a dependent hostThe account cannot be deleted, there are dependent VMs.Delete dependent VMs, repeat account deletion.

5134

There is no suitable node in cluster

There is no suitable node in the cluster for creating or migrating a VM. 

Check if there are enough free resources on the cluster nodes. 

5135

Node has a bad state

Node is unavailable.

Follow the instructions in the If the cluster node is unavailable article.

5137Cluster doesn't have any poolsIP address pools are not connected to the cluster.Connect the IP address pool to the cluster.
5138Selected pools are not connected to the clusterThe selected IP address pools are not connected to the cluster.Connect the IP address pools to the cluster.
5140Some ips from this subnet are used in vmThe subnet contains busy IP addresses.Select another subnet.
5141Ip is activeIP address is used on VM.Select another IP address.
5145Minimal prefix in hetzner datacenter is 24For clusters with the "Routing" configuration type, subnet masks larger than /24 are not supported.Specify a smaller mask.
5146Bad ipv6 subnet prefixIPv6 prefix value is not supported.Specify a prefix value from 32 to 96.
5147No connected IPv6 subnet on nodeThere are no IPv6 subnets on the virtualization node.Create an IPv6 subnet.
5148Not enough free IPv6 blocks on the nodeThere are no free IPv6 blocks on the node.Release the used IPv6 address block.
5149Invalid ssh keyInvalid SSH key.Check the correctness of the SSH key.
5151No disk found for hostNo disk found for VM.Check the correctness of the disk specification.
5152No interface found for hostNo interface found for VM.Check the correctness of the interface specification.
5153ISO count limit exceededThe number of ISO images has been exceeded.Delete some ISO images.
5154ISO size is too bigThe size of the ISO image exceeds the maximum allowed.
  • Perform the action with the Administrator role.
  • Increase the Maximum size of uploaded ISO images parameter in the global system settings. See the article Mounting an ISO image for details.
5155ISO is already mounted to hostAn ISO image is already connected to the VM.Disconnect the connected ISO image.
5156ISO check is failedThe ISO image did not pass the check.Check the integrity of the ISO image.
5159

Backup location check failed

Failed to check the backup storage.Check access to the storage.
5160Operation is not allowed for remotely stored imagesThe operation is not supported for images stored remotely.Select an image in local storage.
5162Backup storage connection check failedBackup storage connection check failed.Check access to the storage.
5163Platform backup schedule have no connected storageNo storage is selected in the platform backup schedule.Select storage in the schedule settings.
5164Failed to open platform backup fileFailed to open the platform backup file.Check the presence and integrity of the file, if necessary, select another file, repeat the operation.
5165Failed to start platform backup processFailed to start platform recovery from backup.Check the presence and integrity of the file, if necessary, select another file, repeat the operation.
5166Bad cron expressionCron record error.Check the cron record format in the schedule settings.
5167Request to service ipmgr failedFailed to execute a request in IPmanager.If integration with an external IPmanager is configured, check the availability of the external IPmanager.

5169

CPU cores number on node exceeds license limit

The number of CPU cores available under the license has been exceeded.

Follow the instructions in the article CPU core number exceeded.

5170VM per node limit exceededThe number of VMs on the node exceeds the limit.Increase the available number of VMs in the node settings.
5171Live migration from newer to older libvirt version not allowedLive migration with these libvirt versions is not supported.Perform migration with VM shutdown.
5172Host is still creatingVM is still being created.Wait for VM creation.
5173Host is in relocation failed stateVM is still migrating.Wait for the migration to complete.
5174Bridge already paired with the host interfaceVM is already connected to the selected bridge.Select another bridge.
5178Node network settings already lockedThe node's network configuration is locked for changes.Wait for the node configuration to change.
5179Iface/Bond can't be paired with more than one Vlanless bridgeThe interface can only be connected to one bridge without VLAN.Disconnect the interface from the connected bridge and reconnect to the required bridge.
5181Node already have default bridgeThe default bridge already exists.Uncheck the "Default bridge for new VM" option for the default bridge and set it for the desired bridge.
5182Invalid slave interface for bridgeThe selected interface cannot be included in the bridge.Select another interface.
5183Interface already included to another bond/bridgeThe selected interface is already included in a bond or bridge.Disconnect the interface from the bond/bridge or select another interface.
5184Cannot remove the default node bridgeImpossible to delete the default bridge.Disable the "Default bridge for new VM" option for the default bridge.
5185Some iface/bond/bridge has already used this nameThe selected interface name is already in use.Select another interface name.
5190Bridge/Bond name matches a reserved patternThis interface name is reserved and cannot be used.Select another interface name.
5193FreeBSD ip automation type only allows 'none' and 'freebsd'For a FreeBSD OS, an IP address assignment model different from freebsd_based or none was selected.Choose the freebsd-based or none type.
5194Linux ip automation type cannot be 'freebsd' or 'windows'The freebsd_based or windows_based IP address assignment model is not supported for this OS.Choose a valid type.
5195Cluster doesn't have any poolsIP address pools are not connected to the cluster.Connect pools to the cluster.
5196Invalid vxlan networkInvalid VxLAN.Select another VxLAN.
5197IP is already allocated in panelIP address is reserved.Select another IP address.
5198IP address not foundIP address not found.Check the correctness of the IP address selection.
5199Create ptr record failedFailed to create PTR record.Check the DNSmanager 6 integration settings and DNS server availability.
5200Update ptr record failedFailed to update PTR record.Check the DNSmanager 6 integration settings and DNS server availability.
5201Delete ptr record failedFailed to delete PTR record.Check the DNSmanager 6 integration settings and DNS server availability.
5202PTR with the same IP already existsA PTR record for this IP address exists.Delete the PTR record in DNSmanager 6.
5203Specified disk is not linked with the specified hostThe selected disk is not connected to the selected VM.Connect the disk to the VM.
5205Cannot change account of disk linked to hostCannot change the owner of a disk attached to a VM.Detach the disk from the VM and change the owner.
5206Disk limit for the specified bus type has been reachedThe number of disks for the selected connection type has been exceeded.Select another connection type.
5207Cannot unlink last host diskImpossible to disconnect the only disk from the VM.Connect an additional disk, make it the main one and disconnect the required disk.
5209Specified host is not on the specified nodeCannot change the prefix of the IPv6 address block allocated for VMs, there are used IPv6 addresses.Release busy IPv6 addresses.
5210Cannot remove disk which linked to hostCannot disconnect a disk that is not connected to the VM.Check the correctness of the disk selection.
5211Cannot unlink main host diskImpossible to disconnect the main disk from the VM.Connect an additional disk, make it the main one and disconnect the required disk.
5212Disk already linked with hostThe disk is already connected to the VM.Check the correctness of the disk selection.
5213Blocked for host with mounted ISOUnavailable for a VM with a connected ISO image.Disconnect the ISO image.
5214Host and disk have to locate on the same nodeVM and disk must be located on the same node.Select one node for the VM and disk.
5215Disk and host have to belong the same accountThe VM and disk must have the same owner.Select one owner for the VM and disk.
5216Linked disk cannot migrate between nodesThe connected disk cannot be migrated between nodes.Disconnect the disk from the VM.
5217Migration destination is equal to sourceThe destination node coincides with the source node.Select another destination node.
5218Node has dependent host backupsThe node has dependent VM backups.Delete dependent backups.
5219Node already existsA node with this name already exists.Select another node name.
5222Disk list must contain an element with boot order equal 1The VM's main disk is not specified.Specify the main disk in the request.
5224Suitable storage is not foundNo suitable storage found.Check the status of storages, if necessary, connect additional storage.
5225Can not migrate between clusters with different datacenter typeImpossible to migrate VMs between clusters with different network setting types.Select a cluster with an identical network setting type.
5226Can not migrate between clusters with different virtualization typeMigration between clusters with different virtualization types is not supported.Choose a cluster of the same type.
5227Can not migrate host with vxlan between clusters with Full Mesh vxlan modeImpossible to migrate VM with VxLAN between clusters with full mesh.Change the cluster configuration or select another cluster.
5228Can not migrate host with vxlan between clusters with different vxlan modeImpossible to migrate VM with VXLAN between clusters with different virtual network types.Change the cluster configuration or select another cluster.
5230The host is protected. It can not be deleted.The VM is protected from deletion.Disable VM protection ("VM Protection Settings" menu item).
5231Several interfaces are not supported for the datacenter with the routing network modelFor the "Routing" network setting type, nodes with two interfaces are not supported.Use one node interface when connecting.
5233

Task registration error

The task cannot be registered.

Repeat the operation that caused the error. If the error occurs again, contact technical support.

5236

Node has libvirt errors

Problems with libvirt daemon on a cluster node. 

Check libvirt using the instructions in the Basic diagnostics article.

5237Node has LXD errorsLXD errors on the node.Check the node's status. Collect logs and contact support.
5238Task cancellation errorThe task was cancelled.Restart the task.
5241The host is protected. No modifications are allowedThe VM is protected from modifications.Disable VM protection ("VM Protection Settings" menu item).

5242

Failed to put SSH-key on node. Check your password or ~/.ssh/authorized_keys on node

An error occurs when trying to copy the platform SSH key to a cluster node or Ceph storage.

  • Check if you can connect to the cluster node or Ceph storage via SSH from the platform server.
  • Check if the following SSH connection settings are correct: server IP address, port and password.
5245You don't have rights to list the snapshots of this hostThe user does not have rights to get the list of snapshots for this VM.Contact the administrator.

5246

Given IP does not belong to any IP-pool assigned to cluster

An error can occur when:

  • attempting to issue an IP address from a network that does not belong to the cluster;
  • receiving information about an IP address that is not found in the database.

Use an IP address from a pool that belongs to the cluster.

5247Anonymization of images is prohibited for a host with an unknown operating systemCannot create an anonymized image for a VM for which: the OS is unknown; the OS group is unknown; the OS group is no_os or rescue.When creating an image, disable the "Anonymize image" parameter.

5248

The specified amount of RAM is less than minimal requirement for this OS

The VM does not have enough RAM to install the selected OS. 

Increase the amount of RAM on the VM. 

5250ISO size value is invalidThe specified ISO image size is less than zero or exceeds the maximum allowed.Pass correct parameters or increase the maximum ISO image size in the "Global Settings" section.
5252Account ID is not providedAccount id is not passed in the request.Specify the correct id in the request.
5254No ISO currently defined for hostISO image is not defined for the VM.Check the specified VM and ISO image parameters.
5257ISO is in mounted state alreadyAn ISO image is already attached to the VM.Detach the ISO image.
5258HA is available only in switching networkHigh availability is not supported in clusters with the "Routing" and IP-fabric configuration types.Create a cluster with the "Switching" configuration type.
5259HA is available only in KVMHigh availability is not supported in LXD clusters.Create a KVM cluster.
5261Storage is not attached to any clusterStorage is not connected to a cluster.Connect the storage to a cluster.
5262One or more ISO from given repository still mounted on cluster VMsCannot delete a storage while there are ISO images attached to cluster VMs.Detach ISO images from VMs.
5263ISO is mounted to hostCannot delete ISO images attached to a VM.Detach ISO images from the VM.
5267Repository already contains ISO with the same nameThe repository already contains an ISO image with this name.Change the name or delete the ISO image.
5269VM is not suitable for master, problems:The VM is not suitable for master-VM. See error text for details.Choose a suitable VM.
5273Overselling limit exceeded for node with masterOverselling on a node with a master-VM must not exceed 1.Specify a permissible overselling value.
5278RAM stick size isn't fit for hot plugRAM increase is only supported with a step of 1024 MB.Specify a permissible RAM value.

5280

Migration of VMs with snapshots between different Network LVM is not allowed.

Migration of VMs with snapshots between different Network LVM is not allowed.

Delete VM snapshots before migration. For more information about migrating VMs with snapshots, see the Snapshots of virtual machines article.

5299Image is not in copyable stateThe image status differs from active, in_use, or copying.Check the image state.
5300Image is not found on nodeUser image not found.Specify correct parameters.
5301Image on node has invalid stateThe image is in one of the following states: deleting, in_use, migrating.Wait for operations to complete.
5302Invalid network maskInvalid network mask.Check the correctness of the network mask input.
5303No suitable networkNo suitable network.Add a network with the required parameters.
5305IP busyIP address is busy.Select another IP address.
5306Not enough free IP in selected poolsNo free addresses.Add an IP address pool.

5308

License expired

License expired.

Check the license expiration date. If the license is valid, activate it.

5309Empty licenseLicense data is missing.Check the license status.
5310Invalid licenseLicense data is corrupted.Re-activate the license.
5313Not enough free IP on nodeNot enough free IP addresses on the node.Allocate more IP addresses.
5314Image Limit ExceededThe limit on the number of images has been reached.Delete unused images.
5315License file expiredLicense data has expired.Check the license status.
5316Only admin can share or set accountOnly the administrator can work with accounts.Contact the administrator.

5319

Nothing to change

The POST request parameters do not change anything. 

Check if the POST request is necessary. If the request is necessary, change its parameters.

5320New disk size incorrectIncorrect new disk size.Specify the correct disk size.

5321

Insufficient space in the storage. Clear space or delete the virtual machines that you don't need

There is not enough free space in the storage.

Delete unnecessary files or virtual machines in this storage.

5322Image limit exceeded for hostThe number of available images for this VM has been exceeded.Delete unused images.
5324Only FSTEC license can be used with FSTEC platform versionFSTEC VMmanager version requires a corresponding license.Use the correct license.
5325Can't delete immortal repositoryDeleting ISPsystem repositories is not supported.No solution.
5326No recipe edit permissionsInsufficient permissions to edit a script.Contact the administrator.
5327Not enough rights for run recipeInsufficient permissions to run a script.Contact the administrator.

5330

Host is crashed

VM is crashed.

Examine the actions that led to the damage to the VM.

5331Limits must be assigned to a role or an accountLimits can only be assigned to a role or an account.Pass the role or account value in the request.
5332Unknown limits levelLimits can only be assigned to a role or an account.Pass the role or account value in the request.
5338Nodes limit exceededLicense limit for the number of nodes exceeded.Check license restrictions and increase limits if necessary.
5339Ippool has used IPImpossible to delete the pool, there are used IP addresses.Release used IP addresses.
5342Empty params for run recipeEmpty parameters for running the script.Specify the required parameters to run.
5343Not enough CPU in nodeNot enough CPU on the node.Reduce the number of vCPUs consumed by the VM, or delete unused VMs.
5344Not enough free RAM in nodeNot enough RAM on the node.Reduce the amount of RAM in VM resources, delete unused VMs or increase the amount of RAM on the node.
5345The network exists but the gateway does not matchThe network exists, but the gateway does not match.Specify the correct gateway for the network.
5349Can not connect with nodeNo connection to the virtualization node.Check access to the virtualization node from the platform server.
5350Could not delete running taskOnly deferred tasks or those in the queue can be deleted.Wait for the task to complete.

5352

No KVM virtualization support on node

The connected cluster node does not support hardware virtualization.

Enable hardware virtualization support in the BIOS/UEFI of the cluster node. 

5353KVM virtualization support is disabled in BIOS settingsHardware virtualization support is disabled in BIOS.Check virtualization settings in the virtualization node's BIOS/UEFI.

5354

Сan not get node info

Unable to get cluster node information.

Check the connection to the cluster node via SSH.

5355Such a hostname is already used for another node in the clusterA node with this name already exists.Select another node name.
5357No host for migrateNo suitable nodes for migration.Check if nodes meet migration requirements.
5356Can not migrate hosts from different clustersBulk migration for VMs from different clusters is not possible.Perform VM migration from each cluster in turn.
5359Can not add the node with active SELinuxImpossible to connect a node on which SELinux is running.Disable the SELinux service on the virtualization node, repeat adding the node.
5360Can not add the node with SELinux enabled in /etc/selinux/configImpossible to connect a node on which SELinux is not disabled in the /etc/selinux/config file.Disable the SELinux service in the /etc/selinux/config file on the virtualization node, repeat adding the node.

5361

Release data unavailable

No access to Changelog messages.

Check access to the Changelog files. If the platform uses a proxy server, check its settings.

5362Disk too small for selected OSInsufficient disk size specified for the selected OS.Increase the VM disk size.
5363Disk too small for selected imageInsufficient disk size specified for the selected VM image.Increase the VM disk size.
5364No email params in licenseThe license does not contain information about default email settings.Check the license status.

5365

Unsupported operating system on node

An unsupported OS is installed on the connecting cluster node.

Install a supported OS and reconnect the node.

5368Ipv6 already enabledAn IPv6 address is already assigned to the VM.Use the existing IPv6 address or remove the IPv6 address from the VM.
5369Ipv6 subnet already exist on nodeAn IPv6 subnet is already assigned to the node.Use the existing subnet or delete it before re-creating.
5370Only one Ipv6 subnet can exist on nodeMore than one IPv6 subnet is specified in the node parameters.Pass only one IPv6 subnet in the request.
5373Hdd overselling is only allowed for file storageDisk space overselling is only supported for file storage, NAS, and ZFS.Choose a supported storage.
5375Week day is not set for weekly scheduleNo day of the week is selected to run the schedule.Select a day of the week.
5376Month day is not set for monthly scheduleNo day of the month is selected to run the schedule.Select a day of the month.
5377Hosts or clusters are not set for scheduleVMs or clusters are not selected in the schedule.Select VMs or clusters.
5366Connection timeoutFailed to connect to the node.Check access to the virtualization node from the platform server.
5371VM is in rescue modeVM is in recovery mode.Disable recovery mode.
5378Start time is not set for scheduleNo start time is selected in the schedule.Select a start time.
5379VM is unavailableVM is unavailable.Check the VM status.
5382vCPU number is not setThe number of vCPUs is not specified.Specify the number of vCPUs.
5383RAM is not setThe amount of RAM is not specified.Specify the amount of RAM.
5384Disk size is not setThe disk size is not specified.Specify the disk size.
5385Not enough rights for fine-tuning settingsNo rights for fine-tuning parameters.Contact the administrator.
5386IP fabric settings is not set for clusterParameters for IP-fabric configuration are not passed.Pass correct parameters in the request.

5387

IP fabric cluster doesn't support the OS

An unsupported OS is installed on the connecting IP-fabric cluster node.

Install a supported OS and reconnect the node.

5388Unsupported operating system on clusterThe operating system is not supported by this cluster type.Choose a suitable OS.
5389Invalid resource valueInvalid resource value.Specify a valid value.
5390Domain change is forbiddenUsers are forbidden from changing the VM's domain name in this cluster.Contact the administrator.
5391Recipe param must have a valueNo value is specified for the script parameter.Specify the parameter value.
5392Unsupported preset of vm on clusterUnsupported VM configuration in the cluster.Select a supported configuration.
5393This OS is not supported on this license typeThis OS is not suitable for this license type.Use a supported OS.
5394No recipient were providedNo recipient of the script execution notification is specified.Specify the notification recipient.
5395Recipient doesn't have languageNo language for the script execution notification recipient is specified.Specify the recipient's language.
5396Recipient doesn't have emailNo email for the script execution notification recipient is specified.Specify the recipient's email.
5397No template was found for specified languageThere is no notification template for the selected language.
  • Add an email template in the missing language.
  • Delete the recipient of the e-mail from the list.
  • Disable sending of the e-mail.
5403LVM is not tunedLVM software is not installed.Install LVM software in the cluster storage.
5404LVM volume group is not setLVM volume group not found.Create a volume group in the LVM software settings.
5405Not found suitable LVM volume group in several VGsNo volume group with a suitable name was found.Specify a name for one of the volume groups that matches the storage settings.
5406Not found LVM volume group with suitable nameNo volume group with a suitable name was found.Specify a name for one of the volume groups that matches the storage settings.
5408Vm storage path not setVM storage path not found.Specify the storage path.
5409Volume group name not setVolume group not specified.Specify the volume group in the cluster settings.
5410OS storage path not setStorage for OS templates is not specified.Specify storage for OS templates.
5411LXD cluster does not support changes for efi_boot parameterLXD clusters do not support bootloader type selection.No solution.

5413

Editing node network settings is not allowed in a cluster with an IP fabric

Changing the network settings of a node in an IP-fabric cluster is not supported.

The operation is not supported.

5416No suitable IPv6 subnet in selected pools

Unable to find a suitable IPv6 subnet for the virtual machine (VM).

  • Add IP addresses to the pools from which the subnet is allocated.
  • Increase the subnet prefix value. 
5502Image creation is not allowedImage creation is prohibited.Contact the administrator.
5504Cpu overselling set lower then 0.5. Try to increase overselling over 0.5CPU overselling is below the allowable level.Set the overselling value to at least 0.5.
5700LXD cluster only supports ZFS storageOnly ZFS storage is supported in LXD clusters.Use ZFS storage.
5701LXD cluster only supports IP-fabric and Switching network configuration typeOnly the "Switching" and IP-fabric configuration types are supported in LXD clusters.Use the "Switching" or IP-fabric configuration type.
5702LXD cluster do not support ISO uploadISO upload is not supported in LXD clusters.No solution.
5703LXD cluster do not support second network interfaceA second network interface is not supported in LXD clusters.No solution.
5706KVM cluster do not support ZFS storageZFS storage is not supported in KVM clusters.Choose a supported storage type.
5707LXD cluster do not support multiple disksLXD clusters do not support working with multiple disks.No solution.
5708LXD cluster do not support network interface editingNetwork interface editing is not supported in LXD clusters.No solution.
5709At least one cluster node is not active now. HA cannot be turned onTo enable high availability, there must be active nodes in the cluster.Check node status.
5902Storage is already attached to clusterStorage is already connected to the cluster.Disconnect the storage from the cluster or use another storage.
5903Storage is not empty on clusterCannot delete or disconnect storage if it contains VM disks.Delete VM disks from the storage.
5904Main storage not found on clusterMain storage is not connected to the cluster.Select one of the storages as the main one.
5905Cluster already has nodes connected with main storage. Can not connect new main storage to clusterThe cluster already has nodes connected to the main storage. Cannot connect a new main storage to the cluster.Use the existing main storage.
5906Storage not found on destination nodeNo storages found on the destination node.Select another destination node.
5907VM storage path is a required parameter for File storageFor file storage, it is necessary to specify the VM storage directory.Specify the VM storage directory.
5908Volume group is a required parameter for LVM storageFor LVM, you need to specify a volume group.Specify a volume group.
5909ZFS pool name is a required parameter for ZFS storageZFS pool name is not specified in the ZFS storage settings.Specify the correct pool name.
5910RBD pool name is a required parameter for Ceph storageFor Ceph, you need to specify the RBD pool name.Specify the RBD pool name.
5911RBD user is a required parameter for Ceph storageFor Ceph, you need to specify the RBD user.Specify the RBD user.
5912Storage params is a required parameter for Ceph storageFor Ceph, you need to specify storage settings.Specify storage settings.
5913IP address is a required parameter for Ceph storageFor Ceph, you need to specify an IP address.Specify the storage IP address.
5914SSH port is a required parameter for Ceph storageFor Ceph, you need to specify the SSH port.Specify the storage SSH port.
5915Storage is disabled on clusterStorage is disabled in the cluster.Enable storage.
5916Main storage is disabled on clusterMain storage is disabled in the cluster.Enable main storage.
5917Can not delete main storage. Cluster has nodesCannot delete main storage while nodes are connected to the cluster.Disconnect cluster nodes.
5918Cluster does not has storagesStorages are not connected to the cluster.Connect storages to the cluster.
5920Storage with same params is already attached to clusterStorage with these parameters is already connected to the cluster.Check the parameters of the connecting storage.

5921

Storage on destination node is not active

The error may occur when selecting a storage with a status other than "Active".

Check the status of the storage. If it is out of service, select another one.

5922Neither ceph nor cephadm utils are not found on the serverNecessary software is not installed in the Ceph storage.Install the necessary software and configure the storage.
5923Repository with the same name already existsA repository with this name already exists.Change the name of the connecting repository.
5924Repository with the same URL already existsA repository with this URL already exists.Change the URL of the connecting repository.
5925Failed to get repository metadataFailed to get repository metadata.Check the correctness and availability of metadata in the repository.

5926

Repository metadata validation failed

Incorrect repository description file metadata.json

Correct the repository description file. 

5927Selected OS is marked for deleteThe selected OS is marked for deletion and cannot be used.Wait for deletion and add the OS again.
5929Selected OS has unsupported network interfaceIncorrect network interface value passed.Pass a correct value. For example, eth0 or ens33.
5931Disk path is a required parameter for Network LVM storageFor Network LVM, you need to specify the disk path.Specify the disk path.
5932Storage type is unknownUnknown storage type passed.Pass correct parameters.
5933Storage does not support HA clusterThe selected storage type is not supported in an HA cluster.Select a supported storage type.
5934Relocation is only allowed for HA clustersVM relocation is only available in high availability clusters.Enable high availability in the cluster.
5936HA is disabled on clusterFailover is disabled in the cluster.Enable failover in the cluster settings.
5939Can not delete node. HA has minimum node countIn an HA cluster, the minimum allowable number of nodes. Impossible to delete a node from an HA cluster..Add nodes to the HA cluster before deleting the target node.
5941Only IP-fabric cluster supports data center traffic exclusionInternal traffic exclusion is only supported for IP-fabric clusters.Specify a cluster with the IP-fabric configuration type in the request. Verify the correctness of the cluster_id and dc_network_id parameters in the request.
5943Range contains in network with empty gatewayNo gateway is specified for the IP address range.Specify the gateway.
5944IP-pool contains network with empty gatewayNo gateway is specified for the IP address pool.Specify the gateway.
5945Default bridge on node not found

Failed to find the default bridge on the node selected to create the VM.

Check if there is a default bridge for the selected network type on the node — primary or secondary.

5947Cannot delete vxlan if it has allocated IPsImpossible to delete VxLAN with used IP addresses.Release busy IP addresses, repeat VxLAN deletion.
5948VxLAN feature disabled on clusterVxLAN usage is disabled in the cluster.Set the "Enable virtual networks" option in the cluster settings.
5950Vxlan settings cannot be set for IP fabric clusterVXLAN setting changes for clusters with the IP-fabric configuration type are not supported.No solution.
5951Vxlan settings is not setVxLAN settings are not specified.Specify VxLAN settings.
5952Vxlan route reflector does not support Bird based IP fabricAttempt to configure VXLAN Route Reflector in a cluster where IP-Fabric uses BIRD.Use FRR for BGP in the cluster with Route Reflector.
5954Storage should be in active stateStorage is not active.Check storage state.
5958License token not foundLicense token not found.Reactivate the license.
5959Update license failedLicense update failed.Check the license status, reactivate the license.
5960Activate license packet failedLicense package activation failed.Check the license package status, reactivate the package.
5962Billing URL is emptyBilling link to BILLmanager is missing.Contact support.
5963License packet is already activated. If activated license packet is not listed in settings, try to update licenseThe license package is already activated.Reactivate the license, check the package status, reactivate the package.
5964Cannot find node with matching host filter paramsFailed to find a node with matching filter parameters.Change filter parameters.

5966

IP address busy

Unable to assign an IP address to the virtual machine.

Change the IP address assignment settings: select a different IP address or address pool. If the address is assigned via DHCP, check the DHCP server settings.

5969Disk backup doesn't belong to diskThis backup does not belong to the disk.Pass correct parameters in the request.
5970Add IP to ipmgr failedFailed to add IP address to IPmanager.Examine log files.
5972Portstart is greater than portendThe start port of the range is greater than the end port.Change the range settings.
5973Filter expression validation failedThe filter value is specified incorrectly.Specify the correct filter value.
5975Host params doesn't match with recipe filtersVM parameters do not match the specified filter.Change filter conditions.
5976Not enough rights to ignore recipe filtersThe user does not have enough rights to ignore filters in scripts.Contact the administrator or disable filter ignoring.
5977Forbidden to pass only recipes, pass additionally hosts or host_paramsThe recipes (script) parameter is passed in the request, but the hosts and host_params parameters are not passed.Add the necessary parameters to the request.
5980Cluster re-import is not available. Cluster is already importedThe cluster is already imported, re-import is not supported.No solution.
5985Migration between Vm5 clusters is not availableMigration between VMmanager 5 clusters is not supported.No solution.
5986Migration from vm6 to Vm5 cluster is not availableMigration from a VMmanager 6 cluster to a VMmanager 5 cluster is not supported.No solution.
5989Migration from VMmgr5 cluster to LXD isn't supportedMigration from VMmanager 5 to an LXD cluster is not supported.Use a KVM cluster.

5991

Ip automation not available


Error can occur when changing the IP address addition model or creating a VM image. 

  • Add missing network interfaces to the guest OS.
  • Add missing IP addresses to the guest OS.
  • Wait for the migration from VMmanager 5 to complete.

5992

Qemu guest agent is not available on host
  • QEMU Guest Agent on the VM is not responding.
  • VM migration with automatic IP address addition failed.

 

5997ISO check timeout is exceededISO image check time exceeded.Check the integrity of the image file, repeat the download.
5999Nodes creation with RedHat and Debian based OS in single cluster is not availableThe platform does not support clusters where nodes with Red Hat-based OS and Debian-based OS are used together.Pass correct parameters.
6000SPICE only available on KVM clusterSPICE is only supported in KVM clusters.Use a KVM cluster.
6001SPICE is disabled on clusterSPICE is disabled in the cluster.Allow SPICE connections in the cluster settings.
6002SPICE is failed on nodeFailed to enable SPICE on the virtualization node.Check the node status.
6004SPICE only available for KVM presetSPICE is only available for VM configurations in KVM clusters.Use a KVM cluster.
6005SPICE is disabled on hostSPICE is disabled on the VM.Allow SPICE connections in the VM settings.
6009Monitoring of this node is not yet started. Please wait for awhile.Node monitoring has not started yet.Wait a while.

6010

Operation is blocked. Node is in maintenance modeAttempting to perform an operation on a node that is in maintenance mode. Wait for the end of the maintenance mode. 

6011

Failed to switch the node to maintenance mode

Failed to switch the node to maintenance mode.

Check if there are restrictions that prevent you from switching the node to maintenance mode.

6012

Maintenance is in bad state for this handler

The cluster node cannot enter or exit maintenance mode. 

Wait for the end of operations that prevent the node from changing state. 
6015Can't initiate maintenance with evacuation when there is one node in clusterCannot perform evacuation when there is only one node in the cluster.Connect an additional node.
6017Maintenance mode was already initializedMaintenance mode has already been initialized.Disable maintenance mode.
6018Maintenance mode is unavailable in HA clusterMaintenance mode is not available in a high availability cluster.Disable high availability.
6019Not enough resources in cluster for evacuation plan, check logsInsufficient resources in the cluster for VM evacuation.Check logs for more detailed information and free up resources.
6020Maintenance mode is unsupported on Routing clusterMaintenance mode is not available for clusters with the "Routing" configuration type.Use the "Switching" or IP-fabric configuration type.
6021Maintenance mode is unsupported on LXD clusterMaintenance mode is not available for LXD clusters.No solution.
6022Only NAS storage is supported for current operationThe operation will only be available when selecting NAS storage.Select NAS storage for the operation.
6023Only local storage is supported for current operationCopying and migration are not available for an image created in NAS storage.Select local storage for copying or migration.
6024Only same NAS storage is supported for current operationThe operation will only be available when selecting NAS storage in which the VM image was created..Select NAS storage with the VM image.
6025Storage params is a required parameter for Nas storageStorage_params, which are mandatory for NAS storage, were not passed in the request.Pass the required parameters.
6026Nas storage path is a required parameter for Nas storageThe "Path to directory on the nodes" parameter is not specified..Specify the parameter value.
6027EFI boot can be set only for NoOSThe OS bootloader cannot be started.Create a VM without an OS to run the bootloader.
6028Unsupported migration for this storage typeMigration is not possible for this storage type: Attempt to migrate a disk to NAS not from file storage or NAS. Attempt to migrate a disk from NAS not to file storage or NAS. Attempt to migrate a disk between two NAS storages.Specify a supported migration type.
6029Only unique NAS storage path can useThe value of the "Path to directory on the nodes" field must be unique.Specify a unique parameter value.
6030VM Balancer feature is not supported on LXD clusterThe balancer is not supported in LXD clusters.Use a KVM cluster.
6031VM Balancer feature is not supported on Routing clusterThe balancer is not supported in clusters with the "Routing" configuration type.Use a KVM cluster.
6032Only infrastructure license type is supportedNAS storage is only supported for the Infrastructure license.Change the license type.
6033Inter-cluster migration from or to a high availability cluster is prohibited.Inter-cluster VM migration in clusters with high availability enabled is prohibited.Disable high availability.
6036No new maintenances in cluster for nodes allowed while existing maintenance with evacuation is not doneThere are nodes in the cluster that are in the evacuation process.Wait for the evacuation process to complete.
6037HA on node cannot be disabled while HA is enabled on clusterAttempt to disable high availability on a node in a high availability cluster.Disable high availability in the cluster.
6038Node does not have HA disabled failed flag setThis method should be used to disable high availability on a node only if disabling high availability in the cluster failed.No solution.
6039SPICE is not available on NoOSSPICE is not available on VMs with NoOS.Install an OS or do not specify the parameter for SPICE.
6041URL of immortal repository cannot be modifiedModifying ISPsystem repositories is not supported.No solution.
6050Not enough rights for create linked-cloneInsufficient permissions to create a linked clone.Contact the administrator.
6051Linked-clone image id not specifiedImage id for the linked clone is not passed in the request.Pass all required parameters.
6052Unsupported linked-clone main disk storage typeUnsupported storage type for a linked clone operation.Select file or NAS storage.
6054The image is used by linked-cloneImpossible to delete the VM image due to created linked clones.Delete the linked clones created based on this image, and repeat the operation.
6056Linked-clone inter cluster migration not availableLinked clone migration between clusters is prohibited.Perform migration without changing the cluster.
6058Linked-clones feature is not supported on this license typeLinked clones are not available for this license type.Change the license type.
6059Linked-clones feature is only available on KVM clusterLinked clones are only available in KVM clusters.Use a KVM cluster.
6060Bridge with such vlan already exists on the selected nodeA bridge for this VLAN already exists on the selected node.Check the passed parameters.
6062New VM migration is forbidden while current migration is not finishedCannot migrate a VM that is in the migration process.Wait for the migration process to complete.
6063Live migration between nodes with inconsistency of OS versionsDatabase record about OS version is incorrect. Migration from a node with AlmaLinux OS below version 8.9 to a node with AlmaLinux OS version 8.9 and above is not supported.Check operating system versions.
6064Live migration between nodes with inconsistency of kernel versionsDatabase record about OS version is incorrect. Migration from a node with OS version kernel 5 or below to a node with OS version kernel 5 and above is not supported.Check operating system versions.
6065Qemu version on destination node should be equal vesion on source node or newerMigration between nodes with a lower QEMU version is not supported.Update QEMU on the target node.

6066

User already exists

A user with this email already exists. 

  • Specify a different email for the user.
  • If the account is created via user invitation, add the user via the Re-invite function (POST request /reinvite).

6067

User does not exist

The user with this email does not exist. 

Check if the email in the request is correct and repeat the request.

6068

Host limit exceeded

The license limit for the number of virtual machines has been exceeded.

Increase your license limit or delete some VMs.

6069Account cannot be deleted. There is a dependent recipeDeleting a user who has dependent scripts is not supported.Change the script owner or delete the user's scripts.
6071Host limit exceededLicense limit for VM creation reached.Increase license limits or delete unused VMs.
6074The master cannot be in a HA cluster while there is node with overselling > 1A master-VM cannot be in a high availability cluster if there are nodes in it with overselling greater than 1.Reduce the overselling value to 1 or lower.
6100Unknown IOMMU deviceThere are no records in the database about the specified PCI device.Check the correctness of the request.
6101Cannot change PCI device mode - device is linked to hostCannot change the mode of a PCI device that is attached to a VM.Detach the device from the VM.
6102Cannot change PCI device mode - device is used by nodeChanging the PCI device mode is not supported for IOMMU Group 0 or if the device is used by a node, not attached to a VM, and not used for vGPU.Check the device status.
6104Cannot passthrough PCI device to VM with balancer. Disable balancer first.PCI device passthrough for a VM with a balancer is not supported.Disable the balancer before passthrough.
6105Cannot enable balancer for VM with PCI passthrough devices. Detach PCI devices first.Cannot enable a balancer for a VM with PCI passthrough devices.Detach PCI devices before enabling the balancer.
6106Cannot migrate VM with PCI passthrough devices.Cannot migrate a VM with PCI passthrough devices.Disable PCI device passthrough.
6107Snapshots not supported for VM with PCI passthrough devices.Cannot create a snapshot for a VM with PCI passthrough devices.Disable PCI device passthrough.
6108Cannot passthrough PCI device to VM with snapshots. Remove all VM snapshots first.Cannot perform PCI device passthrough for a VM with snapshots.Delete snapshots before passthrough.
6109Cannot enable HA for VM with PCI passthrough devices. Detach PCI devices first.Cannot enable high availability for a VM with PCI passthrough devices.Detach PCI devices.
6110Cannot passthrough PCI device to VM with enabled HA. Disable HA first.Cannot perform PCI device passthrough for a VM with high availability enabled.Disable high availability.
6111Not enough GPUs available on the nodeInsufficient graphics processors on the node.Examine logs for more detailed information.

6112

Adding a node with a non-root account is not available for this OS

When connecting a node with AlmaLinux or Ubuntu OS, a user name other than root is specified.

Reconnect the node. Specify the root username.

6113Cannot change PCI device mode - device is failed or its mode already being modifiedPCI device is not ready. The device has failed or its mode is already being changed.Check the device status.
6114Unknown mediated device type (vGPU profile)Unknown vGPU profile type passed.Pass correct parameters.
6115No suitable devices for requested vGPU profileNo suitable device for the vGPU profile.Check the profile and device status.
6118Cannot change PCI device mode - device is used by vGPU deviceCannot change the mode of a PCI device while it is being used for vGPU.Disable vGPU.
6120Snapshots not supported for VM with vGPU.Snapshot creation for a VM with vGPU is not supported.Disable vGPU.
6121Cannot enable HA for VM with vGPU. Detach vGPU profile first.Cannot enable high availability for a VM with vGPU.Detach vGPU.
6122Cannot attach vGPU to VM with balancer. Disable balancer first.Cannot attach vGPU to a VM with an enabled balancer.Disable the balancer.
6123Cannot attach vGPU to VM with snapshots. Remove all VM snapshots first.Cannot attach vGPU to a VM with created snapshots.Delete snapshots from the VM.
6124Cannot attach vGPU to VM with enabled HA. Disable HA first.Cannot attach vGPU to a VM with high availability.Disable high availability.
6125Cannot enable balancer for VM with vGPU enabled. Detach vGPU profile first.Cannot enable a balancer on a VM with vGPU enabled.Detach vGPU.
6126Cannot migrate VM with vGPU.Cannot migrate a VM with vGPU enabled.Disable vGPU.
6128RBAC roles must be specified.Custom (RBAC) roles are not defined.Pass correct parameters.
6129RBAC roles are not found.A non-existent custom (RBAC) role is specified.Pass correct parameters.
6130Groups are not found.A non-existent user group is specified.Pass correct parameters.
6131Bad shebang in scriptIncorrect shebang passed in the script.Use the correct shebang format. 
6132Shebang is not supportedThe passed shebang is not supported.Specify shebang #!/bin/sh or #!/bin/bash
6133Shell script is not supported on WindowsShell scripts are not supported for Windows OS.Check the specified OS. For Windows family OS
6134PowerShell script is not supported on LinuxPowerShell scripts are not supported for Linux OS.Check the specified OS. For Linux family OS
6135A script cannot be shared between Windows and LinuxA script cannot be supported for both Windows OS and Linux OS.Use separate scripts for Linux and Windows: for Linux — Shell, for Windows — PowerShell.
6136Shebang is not supported in PowerShell scripts.A shebang is specified for a PowerShell script.Remove the shebang from the script.
6137Adding a node with a non-root account is not available for this OSAn SSH user with a name other than root is not supported for this OS.Specify the root user.
6138LDAP user cant be edited in VMmanagerAn LDAP user cannot be modified in VMmanager.Modify the user in the LDAP source.
7000Not yet implementedThis operation is not yet implemented.Wait for a product update.

666009

Getting license from server error

Licensing service error. 

Examine the licensing service logs.