cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4219) [UI][Autoscale] Enable/disable in autoscale configuration breaks due to Apply throwing error
Date Mon, 12 Aug 2013 17:58:48 GMT


ASF subversion and git services commented on CLOUDSTACK-4219:

Commit 9c8f040e1a4bdadcb5becad162395b74754017a3 in branch refs/heads/4.2 from [~bfederle]
[;h=9c8f040 ]

CLOUDSTACK-4219: Autoscale UI: Fix for missing form data

Fix form data not being passed when editing autoscale policy on
existing LB rules.

> [UI][Autoscale] Enable/disable in autoscale configuration breaks due to Apply throwing
> --------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4219
>                 URL:
>             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:

View raw message