Bug 101106

Summary: gsm_circularity_ck violation when selecting multiple parties to add to Author role
Product: [Retired] Red Hat Enterprise CMS Reporter: Dennis Gregorovic <dgregor>
Component: otherAssignee: Archit Shah <archit.shah>
Status: CLOSED WONTFIX QA Contact: Jon Orris <jorris>
Severity: medium Docs Contact:
Priority: medium    
Version: nightly   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-11-10 21:00:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 108447    
Description Flags
acs error report none

Description Dennis Gregorovic 2003-07-29 04:38:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716

Description of problem:
In the 'content' content section, I went to Roles/Author/Add Member.  I searched
on 'admin'.  This returned a number of results.  I selected 'Account,
Administrator' (the SWA) and 'content Administration Author'.  I then clicked
'Add Members' and got the constraint violation.  I then successfully added the
Account Administrator user by itself.  I did not try any other permutations.

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

How reproducible:

Steps to Reproduce:
1.see description

Actual Results:  check constraint violated

Expected Results:  constraint not violated and all parties added to the role

Additional info:

Comment 1 Dennis Gregorovic 2003-07-29 04:39:29 UTC
Created attachment 93213 [details]
acs error report

Comment 2 Richard Li 2003-07-29 18:12:37 UTC
retarget for troika errata; not a regression

Comment 3 Archit Shah 2003-08-27 15:46:32 UTC
the Roles/Author/Add Member UI is adding to the "content Administration Author"
group. So you were actually trying to add a group to itself. The violation is
correct. This is a UI bug. It should be cleaned up to fail better.