You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Damodar Reddy T (JIRA)" <ji...@apache.org> on 2014/11/14 09:58:34 UTC
[jira] [Updated] (CLOUDSTACK-7877) The NET.IPRELEASE events are not
added to usage_event on IP range deletion from Physical Networks
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damodar Reddy T updated CLOUDSTACK-7877:
----------------------------------------
Status: Reviewable (was: In Progress)
> The NET.IPRELEASE events are not added to usage_event on IP range deletion from Physical Networks
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7877
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7877
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.3.0, 4.3.1
> Reporter: Damodar Reddy T
> Assignee: Damodar Reddy T
> Fix For: 4.5.0
>
>
> The NET.IPRELEASE events are not added to usage_event on IP range deletion from Physical Networks
> Repro steps:
> ===========
> - Create a zone with Advanced Networking (non Basic)
> - Navigate to Physical Networks
> - Created an IP Range for a physical network and before clicking “Add”, choose to “Add Account”.
> - The range was created and in the cloud database, in the cloud.usage_event table the following events are created:
> {noformat}
> mysql> select id,type,account_id,created,resource_name from cloud.usage_event;
> +----+-------------------------+------------+---------------------+---------------+
> | id | type | account_id | created | resource_name |
> +----+-------------------------+------------+---------------------+---------------+
> (...)
> | 19 | NET.IPASSIGN | 4| 2014-09-12 07:57:36 | 91.198.163.10 |
> | 20 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.11 |
> | 21 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.12 |
> | 22 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.13 |
> | 23 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.14 |
> | 24 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.15 |
> | 25 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.16 |
> | 26 | NET.IPASSIGN | 4| 2014-09-12 07:57:36 | 91.198.163.17 |
> | 27 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.18 |
> | 28 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.19 |
> | 29 | NET.IPASSIGN | 4 | 2014-09-12 07:57:36 | 91.198.163.20 |
> +----+-------------------------+------------+---------------------+---------------+
> {noformat}
> - As you can see it’s assigned to the account_id=4
> - Now, I’ve removed the IP range from the UI and checked the database again.
> - noticed that no records have been added to the table, whereas I’d expect NET.IPRELEASE to have been inserted there for each IP address.
> As a result, the Usage doesn't release the IP in the usage_ip_address
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)