Skip to content

Error: No Destination found for a deployment for VM instance #9576

Closed

Description

@wagnerdracha
ISSUE TYPE
  • Other
COMPONENT NAME

Instances

CLOUDSTACK VERSION

CloudStack 4.19.1.0

CONFIGURATION
OS / ENVIRONMENT

Ubuntu

SUMMARY

On the first time that I create a VM with default cloudstack template (CentOS), it worked perfectly!

But, I uploded a Ubuntu ISO e tried to create a VM with this ISO. After that, cloudstack show the error message: No Destination found for a deployment for VM instance.

I tried to delete the instances and create it again, but after that, I can't create another instance:
image

Looking at management-server.log, I see this message:
2024-08-23 01:14:07,589 INFO [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-2:ctx-f71fceaf job-859 ctx-e1a8ecd5) (logid:b2d52dd2) No destination found for a deployment for VM instance {"id":108,"instanceName":"i-5-108-VM","type":"User","uuid":"d43d952b-a338-4225-955b-568e55b952ca"}: No destination found for a deployment for VM instance {"id":108,"instanceName":"i-5-108-VM","type":"User","uuid":"d43d952b-a338-4225-955b-568e55b952ca"} 2024-08-23 01:14:07,589 DEBUG [o.a.c.a.c.u.v.DeployVMCmd] (API-Job-Executor-2:ctx-f71fceaf job-859 ctx-e1a8ecd5) (logid:b2d52dd2) No destination found for a deployment for VM instance {"id":108,"instanceName":"i-5-108-VM","type":"User","uuid":"d43d952b-a338-4225-955b-568e55b952ca"} com.cloud.exception.InsufficientServerCapacityException: No destination found for a deployment for VM instance {"id":108,"instanceName":"i-5-108-VM","type":"User","uuid":"d43d952b-a338-4225-955b-568e55b952ca"}Scope=interface com.cloud.dc.DataCenter; id=6

I read that error could be a insufficient server capacity, but, you could see that I have resources:
image

To explain how the cloudstack is installed, I have a cloudstack installed on Ubuntu. Primary and Second storage shared on truenas NFS. The mysql was installed in another machine with Ubuntu and running a Galera cluster, and the KVM installed on Ubuntu.

Thnaks in advanced!

Activity

  1. boring-cyborg commented on Aug 23, 2024

    @boring-cyborg

    Thanks for opening your first issue here! Be sure to follow the issue template!

  2. DaanHoogland commented on Aug 23, 2024

    @DaanHoogland
    Contributor

    @wagnerdracha , you'll need to look at the logs above the INFO that you shared to find the reason that no deployment plan could be created.

    As the id of the VM is 108 there have been a lot created before. Check the following;

    • is the ssvm running and the agent connected
    • do the primary storages have capoacity
    • are primary storages reachable for the hosts
    • are there any VMs running in the hosts that are not known to ACS
  3. locked and limited conversation to collaborators on Aug 23, 2024
  4. converted this issue into a discussion #9580 on Aug 23, 2024
  5. added this to the unplanned milestone on Sep 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions