[ https://issues.apache.org/jira/browse/CLOUDSTACK-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695691#comment-13695691 ]
ASF subversion and git services commented on CLOUDSTACK-3255: ------------------------------------------------------------- Commit ab185fb2bf30b970e5d95d491a2003a550332d5c in branch refs/heads/master-6-17-stable from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ab185fb ] CLOUDSTACK-3255: UI > VPC section - IP Address - Load Balancing - autoscale - fix a bug that failed to get zoneid for createAutoScaleVmProfile API. > [UI] [n-tier] CreateAutoscaleVMProfile fails since zoneid parameter is not > being passed from UI - inside a VPC > --------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-3255 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3255 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI > Affects Versions: 4.2.0 > Environment: latest master branch > Hypervisor: Xen server > Reporter: Sowmya Krishnan > Assignee: Jessica Wang > Priority: Critical > Fix For: 4.2.0 > > > Autoscale is practically broken from UI since zone id is not being passed > while creating auto scale vm profile. > This is found while configuring Auto scale for a network tier inside a VPC. > For a non-VPC isolated network, autoscale configuration is working fine. > Since there are lot of configurations in autoscale and it's easier done > through the UI, this is critical. > Steps: > ===== > Create a VPC network with external LB > Create a network tier within the VPC with external LB offering provided by > Netscaler. > Acquire a public IP and configure autoscale with the IP > Input all required configurations for autoscale > Result: > Fails while creating auto scale VM profile due to missing zone id parameter. > Zone id has always been a required param for createAutoScaleVMProfile > Following are the logs > 2013-06-28 02:48:57,321 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===START=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=jso > n&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmg > raceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autosca > leuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > 2013-06-28 02:48:57,344 INFO [cloud.api.ApiServer] (catalina-exec-24:null) > Unable to execute API command autoscalevmprofile due to missing parameter > zoneid > 2013-06-28 02:48:57,345 DEBUG [cloud.api.ApiServlet] (catalina-exec-24:null) > ===END=== 10.252.121.25 -- GET > command=createAutoScaleVmProfile&response=json&sessionkey=KvTOBsg2FgsEC02psvRj7JyKgtY%3D&serviceofferingid=58bbb06a-acff-406f-85e0-47115d368305&templateid=7073aaad-dc82-4ad3-b4b4-ce2f7d945dae&destroyvmgraceperiod=30&counterparam%5B0%5D.name=snmpcommunity&counterparam%5B0%5D.value=public&counterparam%5B1%5D.name=snmpport&counterparam%5B1%5D.value=161&autoscaleuserid=c8d292de-dea3-11e2-9ab7-ca9c098803af&_=1372367747719 > The same works fine while configuring in a non-VPC isolated network -- 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