[
https://issues.apache.org/jira/browse/CLOUDSTACK-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351954#comment-14351954
]
Paul Angus commented on CLOUDSTACK-4192:
----------------------------------------
Hi Francois,
As The 4.1 branch is no longer being maintained, please can you confirm if this
issue is present in any of the 4.3, 4.4 and 4.5 branches which are still being
maintained.
> AutoScaling: More VMs than Maximum are created
> ----------------------------------------------
>
> Key: CLOUDSTACK-4192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4192
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.1
> Reporter: Francois Gaudreault
> Priority: Blocker
>
> In version 4.1.1, autoscaling seems to not care about the maximum instance
> value set in the autoscale policy. I did create a policy with Min:1 and Max:3
> and I was seeing 5 VMs being created in CloudStack.
> Interesting enough, I think there is an issue on the NS side as well since no
> SNMP packets were sent from the NetScaler to the servers to check the load.
> But in any ways, CS should have stop creating VMs when the maximum value was
> hit.
> NS version 10.0 75.70e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
