Hi, Nicolas. Any chance you are using local storage for VM volumes and decreased memory on a certain node? Local storage-based VMs don't have certain migration features to be rebalanced across the nodes. E.g. if you have DATA-volumes attached it cannot be migrated.
ср, 3 окт. 2018 г. в 8:35, Rohit Yadav <[email protected]>: > Hi Nicolas, > > > What is the version of CloudStack you're using? You get this error when > the cluster cpu/memory thresholds have been exceeded and the cluster will > be skipped by the deployment planner for deploying the VM. Check if the > cluster where you were trying to deploy the VM has enough CPU and memory > for the guest VM to run. > > > - Rohit > > <https://cloudstack.apache.org> > > > > ________________________________ > From: Nicolas Bouige <[email protected]> > Sent: Monday, September 17, 2018 7:57:08 PM > To: [email protected] > Subject: Unable to deploy/restart VM > > > Hello All, > > > > On one of my cluster i can’t deploy and/or restart (after cpu/memory > update), the only information i’ve got about the probleme is this message : > > > > Cannot allocate cluster list [1] for vm creation since their allocated > percentage crosses the disable capacity threshold defined at each cluster > at global value for capacity Type : 1, skipping these clusters. > > I checked cluster and global configuration cpu threshold, there are both > with the same value. > > > I was able to restart the impacted Vms with the global admin account as i > could chose the host. > > So why the VMs did not start on the available host ? and Why the error log > appears event if the threshold is not reach on, at least, one of my server ? > > > > Did i miss something ? or do i need to check something else ? > > > Best regards, > > [SignatureBouige] > > > > [email protected] > www.shapeblue.com > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > -- With best regards, Ivan Kudryavtsev Bitworks LLC Cell: +7-923-414-1515 WWW: http://bitworks.software/ <http://bw-sw.com/>
