Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1318918 - Hammer shows incorrect admin status when assign role using user group.
Summary: Hammer shows incorrect admin status when assign role using user group.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Martin Korbel
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 06:49 UTC by Ranjan Kumar
Modified: 2020-07-16 08:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:49:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14261 0 None None None 2016-04-26 17:07:13 UTC

Description Ranjan Kumar 2016-03-18 06:49:01 UTC 
Description of problem:Hammer do not shows correct role status when assigning admin role through user group. 

Version-Release number of selected component (if applicable):6.1.5

Steps to Reproduce:
1. Create a user group called admin-user-group
2. Add admin role to admin-user-group
3. Assign a user to the group admin-user-group.
4. /users page shows that the user has admin rights.
5. Below hammer command shows admin status as No
# hammer -u admin -p <passwd user info --id <user-id>

Expected results:
Hammer user info command should display admin status to yes
Comment 1 Bryan Kearney 2016-04-12 10:14:28 UTC 
Upstream bug component is API
Comment 2 Bryan Kearney 2016-04-12 10:14:31 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14261 has been closed
-------------
Ranjan Kumar
Applied in changeset commit:1cf79b15f0a6af381fa1d9f1b6b9306bbb611fd0.
Comment 4 Martin Korbel 2016-10-20 08:48:04 UTC 
VERIFIED on tfm-rubygem-hammer_cli-0.8.0-1

The parameter "Effective admin" was added in Sat6.3.

Reproducer:
> hammer user create --login "tester" --password "xxx" --mail "root@localhost" --auth-source-id 1
User [tester] created

> hammer user-group create --name admin-user-group --admin yes --users "tester"
User group [admin-user-group] created

> hammer user info --login tester
Id:                   4
Login:                tester
Name:                  
Email:                root@localhost
Admin:                no
Effective admin:      yes
Authorized by:        Internal
Locale:               default
Timezone:             
Last login:           
Default organization: 
Default location:     
Roles:                
    Default role
User groups:          
    admin-user-group
Organizations:        
    Default Organization
Created at:           2016/10/20 07:54:16
Updated at:           2016/10/20 08:51:06
Comment 6 Satellite Program 2018-02-21 16:49:54 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.