Bug 1550487 - Unable to assign a user group more than 20 roles via Hammer CLI
Summary: Unable to assign a user group more than 20 roles via Hammer CLI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.6.0
Assignee: Oleh Fedorenko
QA Contact: Sanket Jagtap
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-01 10:00 UTC by Raashika Raghuwanshi
Modified: 2021-06-10 14:58 UTC (History)
10 users (show)

Fixed In Version: rubygem-hammer_cli_foreman-0.17.0.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 19:47:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 22693 0 None None None 2018-03-01 10:00:51 UTC
Red Hat Knowledge Base (Solution) 3367601 0 None None None 2018-03-01 10:57:47 UTC

Description Raashika Raghuwanshi 2018-03-01 10:00:51 UTC 
Description of problem:
Creating a user-group and assigning it multiple roles is possible on the Satellite GUI but not on the Hammer CLI. It looks like the limit on CLI is 20.

Version-Release number of selected component (if applicable):
Satellite 6.3
tfm-rubygem-hammer_cli-0.11.0-2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. hammer user-group create --name satusergroup --admin true --roles 'Access Insights Admin,Access Insights Viewer,Boot disk access,Compliance manager,Compliance viewer,Create ARF report,Discovery Manager,Discovery Reader,Edit hosts,Edit partition tables,Manager,Organization admin,Red Hat Access Logs,Remote Execution Manager,Remote Execution User,Site manager,Tasks Manager,Tasks Reader,View hosts,Viewer,Virt-who Manager,Virt-who Reporter,Virt-who Viewer'


Actual results:
Could not create the user group:
  Error: one of roles not found

Expected results:
User group satusergroup created

Additional info:
Comment 4 Sanket Jagtap 2019-07-18 12:56:40 UTC 
Build: Satellite 6.6 snap 11

[root@qe-testing-rhel7 ~]# hammer user-group create --name satusergroup --admin true --roles 'Access Insights Admin,Access Insights Viewer,Boot disk access,Compliance manager,Compliance viewer,Create ARF report,Discovery Manager,Discovery Reader,Edit hosts,Edit partition tables,Manager,Organization admin,Red Hat Access Logs,Remote Execution Manager,Remote Execution User,Site manager,Tasks Manager,Tasks Reader,View hosts,Viewer,Virt-who Manager,Virt-who Reporter,Virt-who Viewer'
User group [satusergroup] created.
[root@qe-testing-rhel7 ~]# hammer user-group info --name satusergroup
Id:                   1
Name:                 satusergroup
Admin:                yes
Users:                

User groups:          

External user groups: 

Roles:                
    Virt-who Viewer
    Virt-who Reporter
    Virt-who Manager
    View hosts
    Viewer
    Tasks Reader
    Tasks Manager
    Site manager
    Remote Execution User
    Remote Execution Manager
    Red Hat Access Logs
    Organization admin
    Manager
    Edit partition tables
    Edit hosts
    Discovery Reader
    Discovery Manager
    Create ARF report
    Compliance viewer
    Compliance manager
    Boot disk access
    Access Insights Viewer
    Access Insights Admin
Created at:           2019/07/18 12:55:25
Updated at:           2019/07/18 12:55:25
Comment 5 Bryan Kearney 2019-10-22 19:47:39 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-2019:3172
Note You need to log in before you can comment on or make changes to this bug.