You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/31 15:39:19 UTC
[jira] [Commented] (CLOUDSTACK-2332) [GSLB] deleteAccount is not
cleaning the gslb rules created by the account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671458#comment-13671458 ]
ASF subversion and git services commented on CLOUDSTACK-2332:
-------------------------------------------------------------
Commit 9c0f9aceb8ccfef7b3b5d0a58a619cb8e32f1eea in branch refs/heads/master from Murali Reddy <mu...@gmail.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9c0f9ac ]
CLOUDSTACK-2332:[GSLB] deleteAccount is not cleaning the gslb rules
created by the account
revoking GSLB rules of account on delete
> [GSLB] deleteAccount is not cleaning the gslb rules created by the account
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2332
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2332
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Environment: commit #09af15035b9febe6f55e73a1389f950ab042564f
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> 1. Have at least one account other than admin
> 2. login as the above created account
> 3. Go To regions and create a GSLB rule.
> 4. delete the account
> Observations :
> (i) delete account didn't trigger any "deleteGSLBRules" for the account
> (ii) Here is the snippet from mgmt log related to the account cleanup
> 2013-05-06 06:51:53,699 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-31:job-137) Executing org.apache.cloudstack.api.command.admin.account.DeleteAccountCmd for job-137
> 2013-05-06 06:51:53,738 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Removed account 6
> 2013-05-06 06:51:53,794 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Successfully deleted snapshots directories for all volumes under account 6 across all zones
> 2013-05-06 06:51:53,804 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Expunging # of vms (accountId=6): 0
> 2013-05-06 06:51:53,850 INFO [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) deleteAccount: Deleted 1 network groups for account 6
> 2013-05-06 06:51:53,857 INFO [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) deleteAccount: Deleted 0 affinity groups for account 6
> 2013-05-06 06:51:53,857 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Deleting networks for account 6
> 2013-05-06 06:51:53,860 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Deleting vpcs for account 6
> 2013-05-06 06:51:53,878 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Deleting site-to-site VPN customer gateways for account 6
> 2013-05-06 06:51:53,992 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Account specific Virtual IP ranges are successfully released as a part of account id=6 cleanup.
> 2013-05-06 06:51:53,992 INFO [cloud.user.AccountManagerImpl] (Job-Executor-31:job-137) Cleanup for account 6 is not needed.
> 2013-05-06 06:51:54,016 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-31:job-137) Complete async job-137, jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.response.SuccessResponse@30005187
> (iii) Account got deleted successfully but, we still see the gslb rule in the DB
> 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 |
> +----+--------------------------------------+------------+-----------+-----------+------+-------------+--------+------------+-------------+--------------+------------------+
> | 2 | 3143a2a5-632b-4621-a9c4-10a98f2a64f3 | 6 | 1 | 1 | tmp | tmp | Staged | roundrobin | sourceip | tcp | tmp |
> +----+--------------------------------------+------------+-----------+-----------+------+-------------+--------+------------+-------------+--------------+------------------+
> mysql> select * from account where id=6;
> +----+--------------+--------------------------------------+------+-----------+---------+---------------------+----------------+----------------+-----------------+---------+
> | id | account_name | uuid | type | domain_id | state | removed | cleanup_needed | network_domain | default_zone_id | default |
> +----+--------------+--------------------------------------+------+-----------+---------+---------------------+----------------+----------------+-----------------+---------+
> | 6 | tmp | 99d2bf78-aa15-4014-a056-0d2d81c4db0e | 0 | 1 | enabled | 2013-05-06 10:51:53 | 0 | NULL | NULL | 0 |
> +----+--------------+--------------------------------------+------+-----------+---------+---------------------+----------------+----------------+-----------------+---------+
> Attaching the mgmt server logs and db dump to the bug.
--
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