Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 30F0F200C8C for ; Tue, 6 Jun 2017 13:06:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2F885160BC6; Tue, 6 Jun 2017 11:06:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 76DE1160BC3 for ; Tue, 6 Jun 2017 13:06:22 +0200 (CEST) Received: (qmail 55617 invoked by uid 500); 6 Jun 2017 11:06:21 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 55607 invoked by uid 500); 6 Jun 2017 11:06:21 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 55604 invoked by uid 99); 6 Jun 2017 11:06:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jun 2017 11:06:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4EDA7C1309 for ; Tue, 6 Jun 2017 11:06:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Su6Of3Apr2Wh for ; Tue, 6 Jun 2017 11:06:20 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id CA3CA60EFB for ; Tue, 6 Jun 2017 11:06:19 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E13C7E0DCC for ; Tue, 6 Jun 2017 11:06:18 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 493D721E13 for ; Tue, 6 Jun 2017 11:06:18 +0000 (UTC) Date: Tue, 6 Jun 2017 11:06:18 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9694) Unable to limit the Public IPs in VPC MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 06 Jun 2017 11:06:23 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038625#comment-16038625 ] ASF subversion and git services commented on CLOUDSTACK-9694: ------------------------------------------------------------- Commit cf4cde66f176d267a5bf1039f8722f593446ba49 in cloudstack's branch refs/heads/master from [~rajanik] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=cf4cde6 ] Merge pull request #1850 from sudhansu7/CLOUDSTACK-9694 CLOUDSTACK-9694: Unable to limit the Public IPs in VPC > Unable to limit the Public IPs in VPC > ------------------------------------- > > Key: CLOUDSTACK-9694 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9694 > 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 (v6.3.15#6346)