GitHub user SudharmaJain opened a pull request:
https://github.com/apache/cloudstack/pull/895
CLOUDSTACK-8911: VM start job got stuck in loop looking for suitable â¦
â¦host
VM instance creation job get stuck in the loop, when VMs require local
storage there are host that reached max guest limit and remain hosts does have
storage available. This happens because the hosts that reach the max guest
limit were not getting added to the avoid list and hence the cluster.
Verified the fix on my local setup.
Repro Steps:
1. Take an environment with single cluster and 2 hosts.
2. change the max guest limit for the hypervisor such that on one host max
guest limit should reach.
3. change thresholds so that other host should not have enough storage. If
required create a VM for sufficient bigger disk.
4. Now deploy a VM with local storage.
5. cluster will never be put in the avoid set and job will keep looking for
suitable host.
6. once we increase the max guest limit, VM will deploy or will fail if
there is a lack of storage.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SudharmaJain/cloudstack cs-8911
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/895.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #895
----
commit 17050a07dbcf1ac1430c6b0dae8e415d9fcd5181
Author: SudharmaJain <sudharma.j...@citrix.com>
Date: 2015-09-25T12:35:54Z
CLOUDSTACK-8911: VM start job got stuck in loop looking for suitable host
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
