You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/05/10 08:07:16 UTC
[jira] [Created] (CLOUDSTACK-2435) [GSLB] CloudStack is letting
Admin delete GSLB enabled Netscaler when there are active GSLB rules
venkata swamybabu budumuru created CLOUDSTACK-2435:
------------------------------------------------------
Summary: [GSLB] CloudStack is letting Admin delete GSLB enabled Netscaler when there are active GSLB rules
Key: CLOUDSTACK-2435
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2435
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Reporter: venkata swamybabu budumuru
Steps to reproduce :
1. Have Cloudstack with at least one advanced zone
2. Add a Netscaler and enable it for GSLB
3. Create a GSLB rule and assign at least one LB rule
4. Try to delete the Netscaler which is provisioned and configured with the above GSLB configuration
Observations:-
(i) Though there are active GSLB rules, Netscaler got deleted successfully.
(ii) we still see the GSLB rules and LB rule mapping the DB.
Here is the snippet of mgmt server log and related db tables.
013-05-10 07:26:17,537 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-156:job-298) Complete async job-298, jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.response.SuccessResponse@59a8e0d7
2013-05-10 07:26:17,543 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-156:job-298) Done executing com.cloud.api.commands.DeleteNetscalerLoadBalancerCmd for job-298
2013-05-10 07:26:20,534 DEBUG [cloud.api.ApiServlet] (1451730241@qtp-1391263288-205:null) ===START=== 10.252.241.169 -- GET command=queryAsyncJobResult&jobId=06cbf529-a22c-404f-a4e8-9a296c9ba1db&response=json&sessionkey=F5aip7uDEQvX5xYi2EHQEmN%2FqQo%3D&_=1368165437741
2013-05-10 07:26:20,544 DEBUG [cloud.async.AsyncJobManagerImpl] (1451730241@qtp-1391263288-205:null) Async job-298 completed
mysql> select * from global_load_balancing_rules;
+----+--------------------------------------+------------+-----------+-----------+------+-------------+--------+------------+-------------+--------------+------------------+
| id | uuid | account_id | domain_id | region_id | name | description | state | algorithm | persistence | service_type | gslb_domain_name |
+----+--------------------------------------+------------+-----------+-----------+------+-------------+--------+------------+-------------+--------------+------------------+
| 21 | 05295746-fd66-4e31-9fa3-d2d1349a91f4 | 5 | 2 | 1 | test | test | Active | roundrobin | sourceip | tcp | test |
+----+--------------------------------------+------------+-----------+-----------+------+-------------+--------+------------+-------------+--------------+------------------+
1 row in set (0.00 sec)
mysql> select * from global_load_balancer_lb_rule_map;
+----+--------------+------------+--------+
| id | gslb_rule_id | lb_rule_id | revoke |
+----+--------------+------------+--------+
| 14 | 21 | 7 | 0 |
+----+--------------+------------+--------+
Attaching all the required logs to the bug along with db dump
--
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