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 33C4C200C2A for ; Wed, 1 Mar 2017 10:37:50 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 32673160B78; Wed, 1 Mar 2017 09:37:50 +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 7970B160B70 for ; Wed, 1 Mar 2017 10:37:49 +0100 (CET) Received: (qmail 37140 invoked by uid 500); 1 Mar 2017 09:37:48 -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 37042 invoked by uid 500); 1 Mar 2017 09:37:48 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 37026 invoked by uid 99); 1 Mar 2017 09:37:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2017 09:37:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id E1BD31895B9 for ; Wed, 1 Mar 2017 09:37:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id KtnhDCC6UUao for ; Wed, 1 Mar 2017 09:37:47 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CF6955FB61 for ; Wed, 1 Mar 2017 09:37:46 +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 2941BE0593 for ; Wed, 1 Mar 2017 09:37:46 +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 5AD3F2415E for ; Wed, 1 Mar 2017 09:37:45 +0000 (UTC) Date: Wed, 1 Mar 2017 09:37:45 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9611) Dedicating a Guest VLAN range to Project does not work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 01 Mar 2017 09:37:50 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889851#comment-15889851 ] ASF GitHub Bot commented on CLOUDSTACK-9611: -------------------------------------------- Github user nitin-maharana commented on the issue: https://github.com/apache/cloudstack/pull/1771 @ustcweizhou : You are correct. We have to remove the domain scope. If we support the domain scope, we need more changes on the logic. In that case we can create a new ticket for that. > Dedicating a Guest VLAN range to Project does not work > ------------------------------------------------------ > > Key: CLOUDSTACK-9611 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9611 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Reporter: Nitin Kumar Maharana > > Trying to dedicate a guest VLAN range to an account fails. If we pass both account and projectid parameters to the dedicateGuestVlanRange (which are not mentioned as mutually exclusive in API description) the API layer throws error saying both are mutually exclusive. > Steps to Reproduce: > ================ > Create an account. Create a project in that account. > Go to admin account and change view to the above project. > Navigate to Infrastructure -> Zone -> Physical Network -> Guest -> Dedicate Guest VLAN range. > Try to dedicate the guest VLAN range from the project view for the account associated with the project. > It fails with Error saying accountName and projectId are mutually exclusive. > Expected: > ======== > The VLAN range should get dedicated to the project account. > Notes: > ===== > If we do the dedication from default view then it works fine as no projectid is associated over there. -- This message was sent by Atlassian JIRA (v6.3.15#6346)