Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 6 Oct 2014 22:42:34 +0000 (UTC)
From: "Sheng Yang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12746281.1412635082000.203076.1412635354897@Atlassian.JIRA>
In-Reply-To: <JIRA.12746281.1412635082000@Atlassian.JIRA>
References: <JIRA.12746281.1412635082000@Atlassian.JIRA>
 <JIRA.12746281.1412635082944@arcas>
Subject: =?utf-8?Q?[jira]_[Resolved]_(CLOUDSTACK-76?=
 =?utf-8?Q?75)_Public_IP_accounting_wrong_r?=
 =?utf-8?Q?esult_in_create_VM_due_to_"Maxim?=
 =?utf-8?Q?um_number_of_public_IP_addresses=E2=80=9D?=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7675?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang resolved CLOUDSTACK-7675.
------------------------------------
    Resolution: Fixed

Fixed by:

commit 3201251256817a44b4046c77c170fa82267e3fc3
Author: Anthony Xu <anthony.xu@citrix.com>
Date:   Thu Oct 2 16:02:33 2014 -0700

    ccp should not check public ip resource when deploy a vm on shared netw=
ork


> Public IP accounting wrong result in create VM due to "Maximum number of =
public IP addresses=E2=80=9D
> -------------------------------------------------------------------------=
--------------------
>
>                 Key: CLOUDSTACK-7675
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-767=
5
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Network Controller
>            Reporter: Sheng Yang
>            Assignee: Anthony Xu
>            Priority: Critical
>             Fix For: 4.5.0
>
>
> It's a newly found issue with statistic code.
> Reproduce steps:
> 1. Create a new account, with public ip limit set to 1.
> 2. Login using new account, create a new isolated network(so public ip wo=
uld be used as source nat IP).
> 3. Login as admin, create an shared network. Make sure it's visible to ne=
wly created account.
> 4. Login using new account, create a new VM with the shared network, it w=
ould fail. Complaining maximum public IP reached.
> 5. Create a new VM with both isolated and shared networks, it would fail.=
 Complaining maximum public IP reached.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)