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/06/26 07:26:22 UTC
[jira] [Commented] (CLOUDSTACK-3192) [Dedicated Resources][Public
IP addresses per tenant] Usage Event : NET.IPRELEASE is generated even for
IPs which are in use
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693653#comment-13693653 ]
ASF subversion and git services commented on CLOUDSTACK-3192:
-------------------------------------------------------------
Commit 8a1fefc7aa9290c654859b58f85682126eb7c36a in branch refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8a1fefc ]
CLOUDSTACK-3192. When a dedicated public ip range is released, don't generate usage event EVENT_NET_IP_RELEASE
for ips in the range that are in use becauase these ips are not disassociated from the account.
> [Dedicated Resources][Public IP addresses per tenant] Usage Event : NET.IPRELEASE is generated even for IPs which are in use
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3192
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3192
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Usage
> Affects Versions: 4.2.0
> Reporter: Abhinav Roy
> Assignee: Likitha Shetty
> Fix For: 4.2.0
>
>
> Steps :
> ==============================================
> 1. Add an IP range IP1 to IP10 in Public IP range.
> 2. Dedicated this range to an account.
> 3. Create a network in that account and acquire IPs.
> 4. Suppose IPs acquired are IP1, IP2 and IP3 then create a LB rule on IP1 and leave the other two as it is
> 5. Release the IP range from dedication to that account
> Expected Behaviour :
> ==============================================
> 1. After step 3 a usage event NET.IPASSIGN should be generated for IP1, IP2, IP3
> 2. After step 5 a usage event NET.IPRELEASE should be generated only for IP2 and IP3, not for IP1 as it is still in use.
> Observed Behaviour:
> =============================================
> After step 5 a usage event NET.IPRELEASE is generated for IP1 also, which is not the expected behaviour.
--
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