[
https://issues.apache.org/jira/browse/CLOUDSTACK-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978167#comment-14978167
]
ASF subversion and git services commented on CLOUDSTACK-8911:
-------------------------------------------------------------
Commit 7d46b2ee56e59ade0beeb947271729922ecfc5da in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7d46b2e ]
Merge pull request #895 from SudharmaJain/cs-8911
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.
* pr/895:
CLOUDSTACK-8911: VM start job got stuck in loop looking for suitable host
Signed-off-by: Remi Bergsma <git...@remi.nl>
> VM start job got stuck in loop looking for suitable host
> --------------------------------------------------------
>
> Key: CLOUDSTACK-8911
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8911
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0
> Reporter: sudharma jain
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
