GitHub user wagnerdracha added a comment to the discussion: Error: No Destination found for a deployment for VM instance
@DaanHoogland, thank you for your help! I think I understood what happened (I believe so). My primary storage has 50GB, so in the first example (1 CentOS and 1 Ubuntu instance) that worked, I had 10 GB of HD allocated for CentOS and 30 GB for Ubuntu. So CloudStack "allocated" 40 GB, leaving 10 GB free. In the second example, I deleted the initial instances (CentOS and Ubuntu) and tried to create a new Ubuntu instance with 50 GB of HD, and it worked. However, when I tried to create another new Ubuntu instance with 50 GB of HD, it didn't work. I thought this was possible because when I checked the Primary Storage dashboard, I saw that only 4.59% was used. However, CloudStack must allocate the GB for all instances created to ensure they will work correctly. I think that's how CloudStack works. So, I created a new Primary Storage with 150 GB, and the problem was solved and I was able to create a new instance. Thank you for your help! GitHub link: https://github.com/apache/cloudstack/discussions/9580#discussioncomment-10544282 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
