cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prachi Damle (JIRA)" <j...@apache.org>
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.
Date Fri, 17 May 2013 22:41:15 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661107#comment-13661107
] 

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=cloudstack.git;h=1851f7f ]

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

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.

Changes:
- Even for root-admin make sure that the affinity group and the VM belong to same account
                
> 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. 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2349
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2349
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          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 allowed 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 – vm1 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’s affinity group. But I  can update the
Vm with only affinity group that belongs to the owner Vm. 

--
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

Mime
View raw message