cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4237) [Autoscale] Account deletion doesn't delete all autoscaled LB rules created by the account
Date Sat, 17 Aug 2013 09:02:47 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742882#comment-13742882
] 

ASF subversion and git services commented on CLOUDSTACK-4237:
-------------------------------------------------------------

Commit a03c5f5b1bb3e45b5b2a8365b0c09d48778e426a in branch refs/heads/4.2 from [~rajesh_battala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a03c5f5 ]

CLOUDSTACK-4237 [Autoscale] Account deletion doesn't delete all autoscaled LB rules created
by the account

                
> [Autoscale] Account deletion doesn't delete all autoscaled LB rules created by the account
> ------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4237
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4237
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: 4.2, XS hypervisor, Netscaler as external LB device
>            Reporter: Sowmya Krishnan
>            Assignee: Rajesh Battala
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: mslog, Netscaler_log
>
>
> Steps
> =====
> Create an account, generate API keys for the account
> Login as user and:
> Create Network with offering as Netscaler providing LB service
> Acquire 2-3 public IPs in the account
> Create autoscale LB rule with each of these IPs
> Verify it is created in the Netscaler device as well
> Then, delete the account
> Expected result:
> Should delete all the LB rules created by the account and clean up the server and services
from netscaler.
> Result:
> Only one LB rule is deleted. Rest of the rules although deleted from Cloudstack DB, they
still remain active in Netscaler. Before the LB rules are deleted, the VLAN and n/w bindings
are also removed from Netscaler.
> Here's the status in NS after account deletion is completed:
> > sh lb vserver
> 1)      Cloud-VirtualServer-10.102.196.240-22 (10.102.196.240:22) - TCP Type: ADDRESS
>         State: DOWN
>         Last state change was at Sun Aug 11 13:39:21 2013
>         Time since last state change: 0 days, 00:15:12.490
>         Effective State: DOWN
>         Client Idle Timeout: 9000 sec
>         Down state flush: ENABLED
>         Disable Primary Vserver On Down : DISABLED
>         Appflow logging: ENABLED
>         No. of Bound Services :  0 (Total)       0 (Active)
>         Configured Method: ROUNDROBIN
>         Mode: IP
>         Persistence: NONE
>         Connection Failover: DISABLED
>         L2Conn: OFF
>         Skip Persistency: None
>         IcmpResponse: PASSIVE
>         New Service Startup Request Rate: 0 PER_SECOND, Increment Interval: 0
>         AutoScale Members: 1 (Min)      2 (Max)
> 2)      Cloud-VirtualServer-10.102.196.241-22 (10.102.196.241:22) - TCP Type: ADDRESS
>         State: DOWN
>         Last state change was at Sun Aug 11 13:39:24 2013
>         Time since last state change: 0 days, 00:15:09.670
>         Effective State: DOWN
>         Client Idle Timeout: 9000 sec
>         Down state flush: ENABLED
>         Disable Primary Vserver On Down : DISABLED
>         Appflow logging: ENABLED
>         No. of Bound Services :  0 (Total)       0 (Active)
>         Configured Method: ROUNDROBIN
>         Mode: IP
>         Persistence: NONE
>         Connection Failover: DISABLED
>         L2Conn: OFF
>         Skip Persistency: None
>         IcmpResponse: PASSIVE
>         New Service Startup Request Rate: 0 PER_SECOND, Increment Interval: 0
>         AutoScale Members: 1 (Min)      2 (Max)
>  Done
> Cloud DB:
> mysql> select * from load_balancer_vm_map;
> Empty set (0.00 sec)
> mysql> select * from load_balancing_rules;
> Empty set (0.00 sec)
> mysql> select * from autoscale_vmgroups;
> Empty set (0.00 sec)
> Netscaler DB:
> sqlite> select * from vserver_vm_map;
> 101|Cloud00f0a729e8c1476b81702655dc75bf23|ae8ea870-dc86-4307-9797-53d7f9294f07|10.0.64.83
> 102|Cloudde6dbc0bd97c4252be5d8303438959dd|bffb0b72-6cd1-48a6-8de8-6f11d086b52f|10.0.64.133
> sqlite> select * from servicegroup_info;
> 152|Cloud00f0a729e8c1476b81702655dc75bf23|autoscale-internal_server_Cloud00f0a729e8c1476b81702655dc75bf23|http://10.102.192.203:8080/client/api|ei2f6PY9rFeeXpcz5SM0y-0zmur2psF7rkWoP3jgVBoQRqrPIQuM6KyaJroZnGJc19H3FgNhp-Soq0D2Ol-rjg|KjC88tOXHjwhhf243DB8-1jBO3Z_BttfR8sqgBnnTLq8wqvBQyJrHVjdEAzLYNXZ7tNI7UIChFyY-LKyr8oreA|1
> 153|Cloudde6dbc0bd97c4252be5d8303438959dd|autoscale-internal_server_Cloudde6dbc0bd97c4252be5d8303438959dd|http://10.102.192.203:8080/client/api|ei2f6PY9rFeeXpcz5SM0y-0zmur2psF7rkWoP3jgVBoQRqrPIQuM6KyaJroZnGJc19H3FgNhp-Soq0D2Ol-rjg|KjC88tOXHjwhhf243DB8-1jBO3Z_BttfR8sqgBnnTLq8wqvBQyJrHVjdEAzLYNXZ7tNI7UIChFyY-LKyr8oreA|2
> 156|NONE|NONE|http://10.102.192.203:8080/client/api|ei2f6PY9rFeeXpcz5SM0y-0zmur2psF7rkWoP3jgVBoQRqrPIQuM6KyaJroZnGJc19H3FgNhp-Soq0D2Ol-rjg|KjC88tOXHjwhhf243DB8-1jBO3Z_BttfR8sqgBnnTLq8wqvBQyJrHVjdEAzLYNXZ7tNI7UIChFyY-LKyr8oreA|57

--
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

Mime
View raw message