[
https://issues.apache.org/jira/browse/CLOUDSTACK-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Gaudreault updated CLOUDSTACK-3330:
--------------------------------------------
Priority: Major (was: Critical)
> Autocaling needs a VR to work
> -----------------------------
>
> Key: CLOUDSTACK-3330
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3330
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Reporter: Francois Gaudreault
>
> When you create an autoscaling load balancing rule, and the VR for that
> network haven't been created, you need to spin a VM in order to first create
> the VR, and then the external LB will be assigned, and the autoscaling will
> start working. Is this the expected behaviour? I would expect that if you
> add autoscaling rule, CS would deal with VR creation, and LB assignment.
> Steps to reproduce:
> - Create an isolated guest network, and select a NetScaler Network Offering
> - Create an autoscaling LB rule
> (nothing will happen)
> - The create a VM on that network, and stuff will start to spin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
