Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B7326DAAA for ; Mon, 24 Jun 2013 22:24:21 +0000 (UTC) Received: (qmail 20049 invoked by uid 500); 24 Jun 2013 22:24:21 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 20033 invoked by uid 500); 24 Jun 2013 22:24: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 20025 invoked by uid 500); 24 Jun 2013 22:24:21 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 20022 invoked by uid 99); 24 Jun 2013 22:24:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jun 2013 22:24:21 +0000 Date: Mon, 24 Jun 2013 22:24:21 +0000 (UTC) From: "Alena Prokharchyk (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CLOUDSTACK-3169) [EIP/ELB] [Projects] associateIpAddress fails when executed by non-ROOT admin account from projects view MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Alena Prokharchyk created CLOUDSTACK-3169: --------------------------------------------- Summary: [EIP/ELB] [Projects] associateIpAddress fails when executed by non-ROOT admin account from projects view Key: CLOUDSTACK-3169 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3169 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Affects Versions: 4.2.0 Reporter: Alena Prokharchyk Assignee: Alena Prokharchyk Fix For: 4.2.0 Steps to reproduce : 1. Have at least 1 EIP/ELB enabled zone using the latest 3.0.x code. 2. Create a project 3. Have at least one non-ROOT domain admin as owner of the above project. 4. Execute associate IpAddress API to associate an EIP address Observations: (i) It fails with the following error 2013-06-17 23:01:49,369 DEBUG [cloud.api.ApiServer] (catalina-exec-9:null) (userId=3 accountId=3 sessionId=null) 10.252.112.227 -- GET apiKey=m8y-aWlT5lopDACScCb022A_v0dnRM6-fmYOdqFLDdIzJhyoYY_I1TVauT2wL9fWBpQHMnhLCVF2UdMJ9dbBNQ&command=associateIpAddress&networkid=86ed62de-6250-47c6-b9b3-45dbbc1d7ad1&projectid=ac67765c-e9b0-417a-81e4-0dff71ce00c6&response=json&zoneid=c9c8792b-8bc6-4b60-b32e-6ca7dfb43ff3&signature=2sKP4oCfm87ka6DBrVUmeZQryjk%3D 531 Acct[3-dom1Acc1] does not have permission to operate with resource Acct[1-system] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira