[
https://issues.apache.org/jira/browse/CLOUDSTACK-7675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sheng Yang resolved CLOUDSTACK-7675.
------------------------------------
Resolution: Fixed
Fixed by:
commit 3201251256817a44b4046c77c170fa82267e3fc3
Author: Anthony Xu <anthony...@citrix.com>
Date: Thu Oct 2 16:02:33 2014 -0700
ccp should not check public ip resource when deploy a vm on shared network
> Public IP accounting wrong result in create VM due to "Maximum number of
> public IP addresses”
> ---------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7675
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7675
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> 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 would
> be used as source nat IP).
> 3. Login as admin, create an shared network. Make sure it's visible to newly
> created account.
> 4. Login using new account, create a new VM with the shared network, it would
> 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)
