cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinav Roy (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-2116) [Dedicated Resources : Public IP Addresses per tenant] Able to dedicate more Public IP addresses to an account than it's maximum limit.
Date Thu, 16 May 2013 10:01:23 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinav Roy closed CLOUDSTACK-2116.
-----------------------------------


Closing the bug after verifying the fix on latest master build
                
> [Dedicated Resources : Public IP Addresses per tenant] Able to dedicate more Public IP
addresses to an account than it's maximum limit.
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2116
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2116
>             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
>            Reporter: Abhinav Roy
>            Assignee: Likitha Shetty
>             Fix For: 4.2.0
>
>
> Steps :
> ============================
> 1. Deploy a advanced networking setup.
> 2. Create an account A1 and set the Public IP limits = 5
> 3. Add 4 IP ranges, R1 having 5 IPs, R2 having 3 IPs , R3 having 6 IPs, R4 having 10
IPs.
> 4. Now execute the following cases :
>      Case I   :  Dedicate R1 to A1 and then dedicate R2 to A1
>      Case II  :  Dedicate R1/R2 to A1 and then dedicate R3/R4
>      Case II  :  Dedicate R3/R4 to A1
> Expected Behaviour :
> ===========================
> In Case I    : Dedication of R1 should be successful but R2 should fail as it exceeds
the limits.
> In Case II   : Dedication of R1/R2 should be successful but R3/R4 should fail as it exceeds
the limits.
> In Case III  : Dedication of R3/R4 should fail as it exceeds the limits.
> Observed behaviour :
> ===========================
> In Case I    : Dedication of R1 is successful as expected but R2 also is successful which
is not expected as it exceeds the limits.
> In Case II   : Dedication of R1/R2 is successful as expected and R3/R4  fails as expected
> In Case III  : Dedication of R3/R4 fails as expected.
> Note : we see that only Case I doesn't behave as expected that's because I guess here
we are checking for one single range whose IP set is bigger than the limit and then throwing
the error. We are not actually counting the total no of dedicated IPs to that account and
then comparing it to the allowed limits.

--
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

Mime
View raw message