Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 17 May 2013 22:41:15 +0000 (UTC)
From: "Prachi Damle (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12646309.1367877903914.341713.1368830475712@arcas>
In-Reply-To: <JIRA.12646309.1367877903914@arcas>
References: <JIRA.12646309.1367877903914@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-2349) Anti-Affinity - As admin user
 , using updateVMAffinityGroup() , we are allowed to update the affinity
 group of a Vm (that belongs to a regular user) to be set to admin's
 affinity group.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2349?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D13661107#comment-13661107 ]=20

Prachi Damle commented on CLOUDSTACK-2349:
------------------------------------------

Commit 1851f7f7f6bb4bcf3521ea44c51e9506cb86a72d in branch refs/heads/master=
 from Prachi Damle <prachi@cloud.com>
[ https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;h=3D1851f7f ]

CLOUDSTACK-2365: Anti-Affinity - As admin , we are allowed to deploy a Vm i=
n an affinity group that belongs to different user.

CLOUDSTACK-2349: Anti-Affinity - As admin user , using updateVMAffinityGrou=
p() , we are allowed to update the affinity group of a Vm (that belongs to =
a regular user) to be set to admin's affinity group.

Changes:
- Even for root-admin make sure that the affinity group and the VM belong t=
o same account
               =20
> Anti-Affinity - As admin user , using updateVMAffinityGroup() , we are al=
lowed to update the affinity group of a Vm (that belongs to a regular user)=
 to be set to admin's affinity group.=20
> -------------------------------------------------------------------------=
---------------------------------------------------------------------------=
--------------------------------------
>
>                 Key: CLOUDSTACK-2349
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-234=
9
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Build from master
>            Reporter: Sangeetha Hariharan
>            Assignee: Prachi Damle
>             Fix For: 4.2.0
>
>
> Anti-Affinity - As admin user , using updateVMAffinityGroup() , we are al=
lowed to update the affinity group of a Vm (that belongs to a regular user)=
 to be set to admin's affinity group.
> Steps to reproduce this problem:
> 1.As regular user : create affinity group g1,sg2. Deploy a Vm =E2=80=93 v=
m1 in g1.
> 2.As admin: create affinity group a1,a2.
> 3.As admin, Update Vm1's affinity group to "a1 and a2".
> This succeeds.
> Expected Behavior:
> As admin , I should be allowed to update Vm=E2=80=99s affinity group. But=
 I  can update the Vm with only affinity group that belongs to the owner Vm=
.=20

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira