You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Animesh Chaturvedi (JIRA)" <ji...@apache.org> on 2013/07/24 07:53:49 UTC
[jira] [Updated] (CLOUDSTACK-3369) Autoscaling: Deleting an
isolated network of an account deletes also the autoscaling rule for a
network associated with another account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Animesh Chaturvedi updated CLOUDSTACK-3369:
-------------------------------------------
Fix Version/s: 4.2.0
> Autoscaling: Deleting an isolated network of an account deletes also the autoscaling rule for a network associated with another account
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3369
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3369
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Reporter: Francois Gaudreault
> Assignee: Rajesh Battala
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Hypothesis:
> - Say you have a Network Offering with NetScaler as external load balancer, and you configure it to be shared.
> - Say you have two accounts (A and B), and both have a network using that LB offering
> If you create an autoscaling rule on network associated with account A, and you delete a network associated with account B, it will also delete the autoscaling rule of the network associated with account A.
> To Reproduce:
> - Add a NetScaler, and make it shared (not dedicated)
> - Create a network offering with LB service on the NetScaler
> - Create a network for Account A using the NS network offering
> - Create a network for Account B using the same offering
> - Create an autoscaling rule on network A, and wait until you see VMs spun up by the NS.
> - Spin a VM on network B, and then destroy that VM
> - Delete the Network B
> You should see instances being created with the name VM-Date-NONE.
> Netscaler Logs:
> Jul 4 19:48:36 <local0.notice> 172.30.100.5 Device "server_vip_NSSVC_HTTP_xxxxx:80(Cloud-VirtualServer-74.121.246.141-80)" - State DOWN
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "rm server autoscale-internal_server_Cloud241781113fa541a8aafb46bb45b8a719" - Status "Success"
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "unbind vlan 3654 -ifnum 1/3 -tagged" - Status "Success"
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "unbind vlan 3654 -IPAddress 10.3.96.69 255.255.240.0" - Status "Success"
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "show ns ip 10.3.96.69" - Status "Success"
> Jul 4 19:48:36 <local0.info> 172.30.100.5 Route route(10.3.96.0_255.255.240.0) - State DOWN
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "rm ns ip 10.3.96.69" - Status "Success"
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "show vlan 3654" - Status "Success"
> Jul 4 19:48:36 <local0.info> 172.30.100.5 User nsroot - Remote_ip 172.30.100.15 - Command "rm vlan 3654" - Status "Success"
--
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