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/07/31 18:37:51 UTC
[jira] [Closed] (CLOUDSTACK-3640) [Usage][GSLB] usage events are
not generated for GSLB
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
venkata swamybabu budumuru closed CLOUDSTACK-3640.
--------------------------------------------------
Verified it on the latest CloudStack build and I can see usage_event generated for GSLB rules. closing this bug.
> [Usage][GSLB] usage events are not generated for GSLB
> ------------------------------------------------------
>
> Key: CLOUDSTACK-3640
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3640
> 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: commit # 8cd3a9725ae9b40dc329d53f718f2108bfb6a78c
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce :
> (1) Have the latest CloudStack setup along with usage server running.
> (2) Create at least 2 zones
> (3) Create a GSLB rule with at least 1 LB rule mapping to it.
> (4) verify that the usage event is generated for the GSLB rule.
> Observations:
> (i) Didnt find any event generated for the above GSLB rule.
> here is the snippet of cloud.usage_event.
> mysql> select * from usage_event;
> +----+-------------------------+------------+---------------------+---------+-------------+---------------+-------------+-------------+-----------+----------------+-----------+
> | id | type | account_id | created | zone_id | resource_id | resource_name | offering_id | template_id | size | resource_type | processed |
> +----+-------------------------+------------+---------------------+---------+-------------+---------------+-------------+-------------+-----------+----------------+-----------+
> | 1 | VOLUME.CREATE | 3 | 2013-07-18 13:06:48 | 2 | 15 | ROOT-15 | NULL | 5 | 374730926 | NULL | 0 |
> | 2 | VM.CREATE | 3 | 2013-07-18 13:06:48 | 2 | 15 | Zone2VM1 | 1 | 5 | NULL | XenServer | 0 |
> | 3 | NET.IPASSIGN | 3 | 2013-07-18 13:06:49 | 2 | 16 | 10.147.40.85 | NULL | 0 | 0 | DirectAttached | 0 |
> | 4 | NETWORK.OFFERING.ASSIGN | 3 | 2013-07-18 13:12:47 | 2 | 15 | 55 | 6 | NULL | 1 | NULL | 0 |
> | 5 | SG.ASSIGN | 3 | 2013-07-18 13:12:47 | 2 | 15 | NULL | 2 | NULL | NULL | NULL | 0 |
> | 6 | VM.START | 3 | 2013-07-18 13:12:47 | 2 | 15 | Zone2VM1 | 1 | 5 | NULL | XenServer | 0 |
> | 7 | VOLUME.CREATE | 3 | 2013-07-18 13:38:10 | 1 | 17 | ROOT-17 | NULL | 5 | 374730926 | NULL | 0 |
> | 8 | VM.CREATE | 3 | 2013-07-18 13:38:10 | 1 | 17 | Zone1VM1 | 2 | 5 | NULL | XenServer | 0 |
> | 9 | NET.IPASSIGN | 3 | 2013-07-18 13:38:11 | 1 | 3 | 10.147.44.62 | NULL | 0 | 1 | VirtualNetwork | 0 |
> | 10 | NETWORK.OFFERING.ASSIGN | 3 | 2013-07-18 13:42:57 | 1 | 17 | 59 | 8 | NULL | 1 | NULL | 0 |
> | 11 | VM.START | 3 | 2013-07-18 13:42:57 | 1 | 17 | Zone1VM1 | 2 | 5 | NULL | XenServer | 0 |
> | 12 | NET.IPASSIGN | 3 | 2013-07-18 13:45:45 | 1 | 4 | 10.147.44.63 | NULL | 0 | 0 | VirtualNetwork | 0 |
> | 13 | NET.IPASSIGN | 3 | 2013-07-18 13:46:08 | 1 | 5 | 10.147.44.64 | NULL | 0 | 0 | VirtualNetwork | 0 |
> | 14 | LB.CREATE | 3 | 2013-07-18 13:46:29 | 1 | 1 | NULL | NULL | NULL | NULL | NULL | 0 |
> +----+-------------------------+------------+---------------------+---------+-------------+---------------+-------------+-------------+-----------+----------------+-----------+
> attaching all the logs 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