Description of problem: When working with user/group ownership, there are some scenarios that need clarification. Ramesh summarized the scenarios very nicely in bug 1330022, I'm going to shamelessly copy his work to this bug. " Create the following: Roles: ====== 1. role-1 with no "VM & Template Access Restriction" 2. role-2 with "VM & Template Access Restriction" as "only User Owned" 3. role-3 with "VM & Template Access Restriction" as "Only User or Group Owned" Groups:(Assign all the groups to the same tenant say "My Tenanat") ================================================================== 1. group-1, assign role-1 2. group-2, assign role-2 3. group-3, assign role-3 Users: ====== 1. user-1, assign to group-1 2. user-11, assign to group-1 3. user-2, assign to group-2 4. user-22, assign to group-2 5. user-3, assign to group-3 6. user-33, assign to group-3 Scenario-1: (Working fine as per the new implementation described in comment#8) =============================================================================== login as any user, navigate to Infrastructure Virtual Machines or Cloud Instance. Choose a vm/instance ==> Configuration ==> Set Ownership Result ==> all the users and groups are listed as there is no restriction on the role, which is working fine as per the new implementation Not clear with the below scenario behaviors, need clarification here Scenario-2: =========== 1. As admin, assign a vm or instance to user2 2. Login as user2, only the assigned vm/instance is displayed 3. Choose the vm/instance ==> Configuration ==> Set Ownership 4. Check for the user/group drop down Result ==> only the current user and group he belongs to is displayed (i.e., user-2 & group-2 is displayed) Scenario-3: =========== 1. As Admin, assign a vm or instance to user3 and group3 2. Login as user3 or user33, both of them should be able to see the vm/instance 3. Choose the vm/instance ==> Configuration ==> Set Ownership 4. Check for the user/group drop down Result ==> only the current user and group he belongs to is displayed (i.e., for user 3 ==> user-3 & group-3 is displayed, for user 3 ==> user-33 & group-3 is displayed) So, my question is for Scenario-2 and Scenario-3 Question-1: =========== Why other users belonging to the same group & tenant is not displayed? Reason, being user2 is not able change the ownership to another user who belongs to the same group i.e., user 22. Secondly he is not able to set ownership to another group which belongs to same tenant (which means, user 2 should be able to set ownership to group-1, group-2, group-3) Question-2: =========== As users belonging to group-2 and group-3 will not be able to set ownership to any other user or group, then what is the point of enabling "set ownership" option at all for these groups(this question is the extension for Question-1) " Please define what should be the correct and desired behaviour in the example scenarios. Version-Release number of selected component (if applicable): scenarios working as described in 5.8.0.17 How reproducible: Always Steps to Reproduce: 1. See above scenarios 2. 3. Actual results: QA is not sure if there is a bug in described scenarios or it should work this way. Expected results: Additional info: