You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2013/04/19 17:07:16 UTC
[jira] [Resolved] (CLOUDSTACK-2106) [Dedicated Resources : Public
IP Addresses per tenant]Networks continue to acquire IPs from the Ranges
which are dedicated to other accounts once the IPs in system pool and the
range dedicated to them is consumed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Likitha Shetty resolved CLOUDSTACK-2106.
----------------------------------------
Resolution: Fixed
fixed by commit: f8d4a23343d963ec9d2b9eec8e29f965c2e2198d
branch: master
> [Dedicated Resources : Public IP Addresses per tenant]Networks continue to acquire IPs from the Ranges which are dedicated to other accounts once the IPs in system pool and the range dedicated to them is consumed.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2106
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2106
> 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
> Priority: Critical
> Fix For: 4.2.0
>
>
> Steps :
> ==========================
> 1. Deploy an advanced networking setup, create 4 public IP Ranges R1, R2, R3, R4 and 4 accounts A1, A2, A3
> 2. Now dedicate R1 to A1, R2 to A2, R3 to A3 ( R4 is by default the system pool)
> 3. Now login to A1, create a guest network and start acquiring IP addresses till they are exhausted
> Expected behaviour :
> =========================
> 1. The network should start acquiring from R1 first, once it is consumed it should acuire from R4-the system pool and in case that also is exhaused it should throw an error saying insufficient resources etc.
> Observed behaviour :
> ========================
> 1. The network starts acquiring from R1 then from system pool but once they both are consumed, it doesn't stop and start acquiring from R2,R3 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