GitHub user rajujith added a comment to the discussion: The consoleproxy is not starting and console of the instance not starting, too
@saengraciaEspe Based on the logs cluster 1 does not have free MEMORY capacity to deploy a console proxy VM that needs 1 GB RAM. Could you check your host/cluster free capacity? Is there a cluster or host in disabled state? ``` 2024-06-22 18:17:18,063 WARN [c.c.d.FirstFitPlanner] (Work-Job-Executor-105:ctx-268db4c2 job-1655/job-1760 ctx-41b3df84) (logid:79ff0ac2) Cannot allocate cluster list [1] for VM creation since their allocated percentage crosses the disable capacity threshold defined at each cluster at Global Settings Configuration [name: cluster.memory.allocated.capacity.disablethreshold, value: 0.85] for capacity Type : MEMORY, skipping these clusters 2024-06-22 18:17:18,064 DEBUG [c.c.d.FirstFitPlanner] (Work-Job-Executor-105:ctx-268db4c2 job-1655/job-1760 ctx-41b3df84) (logid:79ff0ac2) No clusters found after removing disabled clusters and clusters in avoid list, returning. ``` GitHub link: https://github.com/apache/cloudstack/discussions/9383#discussioncomment-10030543 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
