Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1057087

Summary: some administrators (admin@internal, admins added via engine-manage-domains?) are displayed with a 'user' icon by mistake.
Product: [Retired] oVirt Reporter: Ondra Machacek <omachace>
Component: ovirt-engine-webadminAssignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: Ondra Machacek <omachace>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, ecohen, emesika, gklein, iheim, mgoldboi, yeylon
Target Milestone: ---Keywords: Regression
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: ovirt-3.4.0-beta3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:27:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen-shot: admin icon vs. user icon none

Description Ondra Machacek 2014-01-23 12:47:33 UTC
Description of problem:
When user is added with -addPermissions parametr via engine-manage-domains command, then user has incorrect icon.
User has userrole icon not adminrole icon. (only under users tab) 

Version-Release number of selected component (if applicable):
ovirt-engine-3.4.0-0.5.beta1.fc19.noarch

How reproducible:
always

Steps to Reproduce:
1. engine-manage-domains -action=add -domain=mydomain.com -user=my_admin -interactive -addPermissions -provider=IPA
2. Check icon of user in users tab in webadmin

Actual results:
user has user icon

Expected results:
user has admin icon

Additional info:

Comment 1 Ondra Machacek 2014-01-23 13:00:25 UTC
admin@internal has wrong icon too

Comment 2 Einav Cohen 2014-01-24 18:34:20 UTC
Created attachment 855149 [details]
screen-shot: admin icon vs. user icon

Comment 3 Einav Cohen 2014-01-24 18:38:06 UTC
(In reply to Ondra Machacek from comment #1)
> admin@internal has wrong icon too

indeed (see attachment 855149 [details] left-hand side is a screen-shot from my setup, right-hand side is the way that it should be). 
so this is probably not related to engine-manage-domains at all - it seems that administrators are displayed in the GUI as users (i.e. with a 'user' icon), for some reason -> changing BZ subject accordingly.

Comment 4 Ondra Machacek 2014-01-25 17:17:06 UTC
If I add admin user from domain via for example Clusters->Permissions(or others)
 then the admin user has correct icon. So I think it has something to do with 
 manage-domains. Also icons are displayed correctly in Clusters->Permissions(and
 others) subtab.

Comment 5 Einav Cohen 2014-01-26 01:25:16 UTC
(In reply to Ondra Machacek from comment #4)
> If I add admin user from domain via for example Clusters->Permissions(or
> others)
>  then the admin user has correct icon. So I think it has something to do
> with 
>  manage-domains. 

unless I am missing something, manage-domains has nothing to do with the admin/internal user/domain (I could be wrong). Maybe there is a problem in both the admin@internal user and the manage-domains tool - not sure. 

> Also icons are displayed correctly in
> Clusters->Permissions(and
>  others) subtab.

the icon in the Permissions sub-tabs represent the type of the permission, which is the type of the Role associated with the permission, not the type of User assigned to the permission: a User permission is a permission that is associated with a User role and it is represented by the User icon. an Admin permission is a permission that is associated with an Admin role and is represented by the Admin icon. It has nothing to do with the user: A permission can be a User permission (i.e. a permission that is associated with a User role) and be displayed (correctly) with the User icon, even if it is assigned to an admin user. 

so the fact that the icons are displayed correctly in the Permissions sub-tabs has nothing to do with the reported problem.

Comment 6 Itamar Heim 2014-01-26 08:11:46 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 7 Martin Perina 2014-02-16 12:58:05 UTC
Not yet merged into ovirt-engine-3.4

Comment 8 Sandro Bonazzola 2014-02-19 12:27:42 UTC
This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA

Comment 9 Ondra Machacek 2014-02-25 09:09:11 UTC
Ok in ovirt-3.4.0-beta3.

Comment 10 Sandro Bonazzola 2014-03-31 12:27:45 UTC
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released