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] [Assigned] (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.
Date Fri, 14 Jun 2013 18:48:19 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prachi Damle reassigned CLOUDSTACK-2350:
----------------------------------------

    Assignee: Jessica Wang  (was: Prachi Damle)

The changes were always presnt in master - the parameters are not seen in the listAffinityGroupsCmd
because they are in the base class.
                
> 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: Jessica Wang
>             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

Mime
View raw message