You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/05/13 23:45:17 UTC

[jira] [Comment Edited] (CLOUDSTACK-2350) Anti-Affinity - As admin user, when tryinto update the affinity group for a Vm that is deployed by a regular user , he is presented with admin's affinity groups.

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

Sangeetha Hariharan edited comment on CLOUDSTACK-2350 at 5/13/13 9:43 PM:
--------------------------------------------------------------------------

Using listAffinityGroups()  call , Admin is not able to list affinity groups of other accounts by passing account and domainid parameter. 
                
      was (Author: sangeethah):
    Using API call , Admin is not able to list affinity groups of other accounts by passing account and domainid parameter. 
                  
> Anti-Affinity - As admin user, when tryinto update the affinity group for a Vm that is deployed by a regular user , he is presented with admin's affinity groups. 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2350
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2350
>             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, when tryinto update the affinity group for a Vm that is deployed by a regular user , he is presented with admin's affinity groups.
> Steps to reproduce the 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.Stop vm1.
> 4. Try to update vm1’s affinity group. List of affinity group shown here is “a1,a2”.
> Expected Behavior:
> List of affinity group should include the affinity groups that belongs to the Vm's owner account.

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