cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9694) Unable to limit the Public IPs in VPC
Date Tue, 01 Aug 2017 19:20:03 GMT


ASF subversion and git services commented on CLOUDSTACK-9694:

Commit f8f71a5af6dced67471935ca4744662f9e7c32de in cloudstack's branch refs/heads/master from
[;h=f8f71a5 ]

CLOUDSTACK-9694: Unable to limit the Public IPs in VPC

Added missing clause to check for vpc_id

(cherry picked from commit cdf2b0727a653f71c2ea10be1b46d2002f88a2e3)
Signed-off-by: Rohit Yadav <>

> Unable to limit the Public IPs in VPC
> -------------------------------------
>                 Key: CLOUDSTACK-9694
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.9.0
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
> Unable to limit the Public IPs in VPC.
> In VPC network, while acquiring the IP addresses, in the resource_count table, count
for the domain is getting increased. However, when the resource count is updated at Domain
level, resource count is getting reverted to only non-vpc ip count.
> Steps to Reproduce:
> 1. Create a VPC
> 2. Create a VPC tier.
> 3. Check resource_count table and note the ip address count. (say 1) 
> 4. Keep acquiring the IP addresses, (say 4 IP addresses). Now new ip address count resource_count
table is 5.
> 5. update the resource count at domain level.
> 6. the resource_count is updated back 1

This message was sent by Atlassian JIRA

View raw message