Nitin Mehta created CLOUDSTACK-4941:
---------------------------------------
Summary: CLONE - Allocation capacity of a cluster during HA
Key: CLOUDSTACK-4941
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4941
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.2.0
Reporter: Nitin Mehta
Assignee: Nitin Mehta
Priority: Critical
Fix For: 4.2.1
When the host goes down. Cloudstack will stop the VM's for which HA is not
enabled. Once cloudstack marks these VM's as stopped then the capacity of these
VM's is moved into the reserved capacity.
If the VM's are HA enabled then cloudstack will stop and start the VM's on
another host. During this time the capacity of the VM's will be moved to
reserved capacity once the VM's are stopped, But when the Vm's are being
started cloudstack will try to calculate what will be total allocated capacity
if the VM is started again ( even though the CPU for the VM is already
reserved). This is a bug in cloudstack where the CPU required for the VM is
considered twice when calculating the allocated capacity.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
