You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Abhinav Roy (JIRA)" <ji...@apache.org> on 2013/07/03 11:06:20 UTC

[jira] [Closed] (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:all-tabpanel ]

Abhinav Roy closed CLOUDSTACK-3192.
-----------------------------------


Closing the bug after verifying the fix with the latest stable branch build
                
> [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