[ https://issues.apache.org/jira/browse/CLOUDSTACK-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prachi Damle resolved CLOUDSTACK-2349. -------------------------------------- Resolution: Fixed > 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