[
https://issues.apache.org/jira/browse/CLOUDSTACK-9235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109503#comment-15109503
]
ASF subversion and git services commented on CLOUDSTACK-9235:
-------------------------------------------------------------
Commit ce4ea45ce04b3d4b82dd1351d12457c836d452dd in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ce4ea45 ]
Merge release branch 4.7 to master
* 4.7:
CLOUDSTACK-9237: Create LB Healthcheck issues - button alignment and error
message goes outside the window
CLOUDSTACK-9235: Autoscale button is missing in VPC
CLOUDSTACK-9229: Autoscale policy creation failing in VPC due to zoneid
missing in createAutoScaleVmProfile
> Autoscale button is missing in VPC
> ----------------------------------
>
> Key: CLOUDSTACK-9235
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9235
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Nitin Kumar Maharana
>
> Autoscale button is missing. This should not be the case since we are able to
> add NS as the external LB provider in VPC.
> Steps:
> =====
> 1. Create a VPC offering with NS as the external LB provider
> 2. Create a VPC and configure the public tier with the above offering
> 3. Acquire an IP address and try to configure Load Balancing rule
> Result:
> ======
> Autoscale option is not visible at all for the LB.
> Expected Result:
> =============
> Autoscale option should be available and should work exactly like the way it
> works for a normal isolated network with NS. If we choose NS as service
> provider for LB, autoscale should also be visible. If VR is chosen, only then
> we should not display autoscale.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
