cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajesh Battala" <>
Subject Review Request 13534: Autoscaling: Deleting an isolated network of an account deletes also the autoscaling rule for a network associated with another account
Date Tue, 13 Aug 2013 10:23:46 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for cloudstack, Devdeep Singh, Murali Reddy, Ram Ganesh, and Vijay Venkatachalam.


Repository: cloudstack-git


if  autoscale policies are created by CS , then when any network gets deleted which got created
with Netscaler as LB provider, the autoscale servers are getting deleted.

during delete the network ipassoc cmd executed on Netscaler resouce is cleaning up the services
which are present in the same subnet. 
NetUtils.sameSubnet(vlanSelfIp, server.get_ipaddress(), vlanNetmask) is returning true for
the autoscale servers even they are not present in the subnet because this method is returning
true if any any of the ip is true.

autoscale server don't have ip address, so true is returned and hence removing the autoscale
servers. which is causing severe issue for the autoscale policies created in cloudstack.


while executing the method deleteServersInGuestVlan which will clean up the servers present
in same subnet, check is made not to delete the autoscale servers.





created accounts testa testb and created networks with NS as LB provider network offering.

1. In TestA, created autoscale policy and wait for deploy the instance. policy got created
and vm got deployed.
2. Delete the testB network, check in ns.log that autoscale servers won't get delete.
3. in testB network, create LB rules, and delete the network, verified autoscale servers won't
get delete.
4. Destroy testA, TestB network, first rules got cleaned up and then the ip assocations of
the network are removed.


Rajesh Battala

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message