[
https://issues.apache.org/jira/browse/CLOUDSTACK-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13656424#comment-13656424
]
Sangeetha Hariharan commented on CLOUDSTACK-2350:
-------------------------------------------------
Also, when admin calls listAffinityGroups() with out account and domainid
parameter, all affinity groups belonging to all users need to be returned.
> 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
