Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 116227 - Roles are appearing as Groups
Roles are appearing as Groups
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Daniel Berrange
Depends On:
  Show dependency treegraph
Reported: 2004-02-19 04:30 EST by James Kearns
Modified: 2007-04-18 13:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-19 05:16:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Kearns 2004-02-19 04:30:37 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
When I create a new role under the Roles tab, I notice this appears 
in Groups under the User Administration, Groups tab.
Then when I go to Add Members to the Role, search returns these Roles 
as Groups. I expect to set privileges by Role, not Group. 

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

How reproducible:

Steps to Reproduce:
1. Create Role
2. Go to Groups
3. A new Group has appeared

Actual Results:  1. Created a role called "Jurassic editor"
2. Can now see a new Group. "Group Name: content Administration 
Jurassic editor"
3. This appears in Member search results for Groups 

Expected Results:  I expect Roles to be different from Groups. One 
would not create the other.

Additional info:
Comment 1 Daniel Berrange 2004-02-19 05:16:33 EST
Roles are just a convenience in CMS for associating a group with a
bunch of permissions. As such when you create a Role, it internally
creates a group, which you can then see in Groups tab at /ccm/admin.
This is the expected behaviour of the system.

Note You need to log in before you can comment on or make changes to this bug.