[ https://issues.apache.org/jira/browse/CLOUDSTACK-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jessica Wang reassigned CLOUDSTACK-4219: ---------------------------------------- Assignee: Brian Federle Brian, I just tested it on my machine (with the database dump provided in this bug). This bug can be reproduced by just clicking "Apply" button in autoscaler dialog. i.e. don't need to click "Disable" first and don't need to change any value in autoscaler dialog. Just click "Apply" button and JS error will appear like my attachment "jessica_1.jpg", "jessica_2.jpg". This seems to be a recent regression in widget code..... Jessica > [UI][Autoscale] Enable/disable in autoscale configuration breaks due to Apply > throwing error > -------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-4219 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4219 > 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: 4.2 Branch, NS as external LB device > Reporter: Sowmya Krishnan > Assignee: Brian Federle > Priority: Critical > Fix For: 4.2.0 > > Attachments: cloud.dmp, jessica_1.jpg, jessica_2.jpg > > > For updating any Autoscale config, we need to first disable AutoscaleVMgroup > and then make the changes and enable the VMgroup again. > Currently this is working fine through API > From UI, the same is broken since after disabling Autoscale config, updation > doesn't work: Clicking on Apply throws the following error: > (Firebug log): > TypeError: formData is undefined > http://XXXX:8080/client/scripts/ui-custom/autoscaler.js?t=1376068487788 > Line 361 > After enabling back autoscale the updated configuration is not applied. > Steps: > Network-> IP Addresses -> Load Balancing - View All -> Autoscale -> Configure > Disable autoscale > Update any of the config -- 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